Start a scenario by using the command line
You can start a scenario by using the HCL OneTest™ API command line. This option is useful in situations where Ant is not available.
IntegrationTesterCmd Options start-scenario
An example syntax for synchronous mode:
IntegrationTesterCmd --serverUrl "https://Host name or IP address:5443/RTCP/"
--domain <Domain name> --environment <Environment name>
--name <Scenario name> start-scenario
An example syntax for asynchronous mode:
IntegrationTesterCmd --serverUrl "https://Host name or IP address:5443/RTCP/"
--domain <Domain name> --name <Scenario name>
--owner <Owner name> --username <User name> --force
--async --stopStubs ALL start-scenario
The following table lists the options that you can use with the IntegrationTesterCmd
command
for starting a scenario.
Option | Description |
---|---|
--serverUrl/-u | URL of the HCL Quality Server. |
--domain/-d | Domain name |
--environment/-e | Environment name |
--name/-n | The name of the target scenario to start. |
--owner/o | Filters the scenarios by owner (optional). |
--stopStubs | Available settings are as follows:
|
--async/-a | Run asynchronously; defaults to synchronous (flag). |
--force/-f | Attempt to first stop any scenario that is already running in the environment (flag). |
--username/-l | Specify the user name to authenticate with the server if the environment is locked and the domain security is disabled. |
--securityToken | Specify the security token generated for the user to authenticate with HCL Quality Server when the domain security is enabled. In the locked environment mode, the operation can be performed by the user who locked the environment. For more information, see Domain level security and Managing environments. |
Scenario selection
For a description of how to select a scenario, see Scenario selection.
Error codes
For details of any error codes, see Exit codes for Command-line client and Ant client.