Configure additional KRE arguments
Additional KRE Arguments let you pass extra Katalon Runtime Engine (KRE) command-line arguments to Test Execution - Cloud when you create an automated test run.
- This feature is available only for cloud-hosted environments.
Configure additional KRE arguments​
- Navigate to Executions and select + Create > Create Automated Test Run.
- Fill in the test run details and select your cloud-hosted configuration.
- Expand Advanced Settings.
- In the Additional KRE Arguments field, enter the additional KRE arguments you want to pass to KRE.
Example:
-retry=1
-g_Environment="staging"
- Save or run the test run.
Restricted arguments​
Some KRE arguments are managed by Test Execution - Cloud and cannot be overridden through Additional KRE Arguments.
Arguments with the following prefixes are not allowed:
-proxy.*-testOps.*
Examples:
-proxy.auth.option=NO_PROXY
-testOps.jobUUID=12345
General arguments that are not allowed:
-executionProfile-testSuitePath-testSuiteCollectionPath-testSuiteCollectionQuery-retryStrategy-browserType-webui.autoUpdateDrivers-executionUUID-serverUrl-orgId-orgID
FAQs​
Why these arguments are restricted?​
Test Execution - Cloud automatically manages execution settings required for cloud execution. These settings ensure that your executions run correctly, connect to the appropriate infrastructure, and report results accurately.
Examples of system-managed values include:
-browserType=Remote
-executionProfile=<selected profile>
-testSuitePath=<suite path>
-testSuiteCollectionQuery=<collection query>
-apiKey=<generated key>
-orgID=<organization id>
-serverUrl=<server url>
-executionUUID=<execution id>
-testOps.jobUUID=<job id>
-proxy.auth.option=NO_PROXY
-webui.autoUpdateDrivers=false
What happens if you provide a restricted argument?​
Restricted arguments are filtered out and are not included in the generated KRE command. Test Execution - Cloud continues using its system-managed values for those settings.