Properties of Steps

You must set the properties of steps to run the tests.

Input properties for the test run step

Field Type Description
Name String Required. Enter the name of the step.
Config File String Optional. The complete path to a file that contains the parameters for a test or schedule run.
Custom Report Format Files String Optional. A comma-separated list of absolute paths to custom report format files (.view files) to use when exporting statistical report data with the -exportstats option.
Exported HTTP Test log File String Optional. The complete path to a file in which to store the exported HTTP test log.
Exported Statistical Report Data File String Optional. The complete path to the directory in which to store exported statistical report data.
Installation Manager Shared Location String Required. Complete path to IBMIMShared Shared location. By default, on Windows™, this is at C:\Program Files\__VENDOR_NAME__\__VENDOR_NAME__IMShared\
Project String Required. The path, including the file name of the project relative to workspace.
Quiet Boolean Optional. Turns off any message output from the launcher and returns to the command shell when the run or the attempt is complete.
Results File String Optional. The name of the results file. The default result file is the test or schedule name with a time stamp appended.
Overwrite Results file Boolean Optional. Determines whether a results file with the same name is overwritten. The default value is true which indicates that the results files can be overwritten.
Test Suite Name String Required. The path, including the file name, of the test to run relative to the project. A test can be WebUI test, Compound test, Performance Schedule or Accelerated Functional Test. To run multiple tests sequentially, specify test names separated by comma.
Note: You must provide the file name along with the file extension if you are using an Accelerated Functional Test suite.
User Comments String Optional. Add text within double quotation mark to display it in the User Comments row of the report.
VM Args String Optional. Java™ virtual machine arguments to pass in.
Protocol Input String Optional. You can use this argument to run a Web UI test in parallel on different browsers.

-protocolinput "all.available.targets.in.parallel=all"

-protocolinput "all.available.targets.in.parallel=chrome,ff,ie"

Note: If you use the -protocolinput argument, you must not use the equivalent -vmargs arguments:
-vmargs "-Dall.available.targets.in.parallel=all"
-vmargs "-Dall.available.targets.in.parallel=browser1,browser2,browser3"
Var File String Optional. The complete path to the XML file that contains the variable name and value pairs.
Workspace String Required. The complete path to Eclipse workspace.
Number of Virtual Users String Optional. For a schedule, the default value is the number of users specified in the schedule editor. For a test, the default value is one user. Overrides the default number of users, if required.
Dataset Override String Optional. For a test, the default value is the dataset specified in the test editor.
Note:

You must use the Dataset Override option to replace the dataset values during a test run. You must ensure that both original and new datasets are in the same workspace and have the same column names. You must also include the path to the dataset.

For example,

/project_name/ds_path/ds_filename.csv:/project_name/ds_path/new_ds_filename.csv.

You can swap multiple datasets that are saved in a different project by adding multiple paths to the dataset separated by a semicolon (;).

For example, 

/project_name1/ds_path/ds_filename.csv:/project_name1/ds_path/new_ds_filename.csv;
/project_name2/ds_path/ds_filename.csv:/project_name2/ds_path/new_ds_filename.csv