Start a scenario by using an Ant task
You can start a scenario by using the HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) Ant tasks.
Here is an example
syntax:
<taskdef name="startScenario" classname="com.ghc.ghTester.ant.StartScenario" classpathref="tasklib" />
<startScenario domain="<Domain name>" environment="<Environment name>" name="<Scenario name>"
serverUrl="https://Hostname or IP address:5443/" />
The following table lists the attributes that can you can use with the
startScenario
Ant task for starting a scenario.
Attribute | Description | Required |
---|---|---|
async | Run asynchronously (flag). | No, default is synchronous. |
domain | Domain name | Yes |
environment | Environment name | Yes |
failureProperty | The name of a property that is set in the event of a failure. | No |
force | Attempt to first stop any already-running scenario in the environment (flag). | No, default is false. |
haltOnFailure | Set to true to fail the Ant script if the scenario fails to start (flag). | No, default is false. |
name | The name of the target scenario to start. | No |
owner | Filters the scenarios by owner. | No |
securityToken |
Specify the security token generated for you to authenticate with Test Virtualization Control Panel when the domain security is enabled. In the locked environment mode, the operation can be performed by the user who locked the environment. |
No, default is to send no token. |
serverUrl | URL of the Test Virtualization Control Panel | Yes |
stopStubs | Available settings are as follows:
|
No, default is NONE |
username | Specify the user name to authenticate with the server if the environment is locked and the domain security is disabled. | No |
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.