The command has two distinct usages: By specifying all the arguments on the command line, and by using a parameter file to specify one or more configurations.
When you run a single configuration (specified by the -environment, -run, and -project arguments), you can specify all the arguments on the command line. Here is an example
RunTests [-licence key] [-noHTTP] [-noResultsPublishers]
[-useResultsPublishers pub_1,pub_2] [-resultsServerLogging absolute|relative|ignore]
-environment <environment name or ID> -project <file> -run "res_1;res_2"You can also use a parameter file to specify one or more configurations. Here is an example:
RunTests [-licence key] [-noHTTP] [-noResultsPublishers]
[-useResultsPublishers pub_1,pub_2] [-resultsServerLogging absolute|relative|ignore]
-parameterFile fileFor example:
C:\> "C:\Program Files\IBM\RationalIntegrationTester\RunTests"
-noHTTP
-useResultsPublishers MyPub,TIB_Pub -resultsServerLogging ignore
-environment HotelApp -project
C:\RationalIntegrationTesterProjects\HotelApp\HotelApp.ghp -run
"HotelApp/Airline/booking/MakeBooking/CardType = Visa"| Parameter | Description |
|---|---|
| -environment <name> | The name or ID of the Rational Integration Tester environment
to use when running the test items. Note: The internal ID field in
the Documentation tab of the environment represents the environment
ID that can be used as an alternative for the environment name.
|
| -input | Path to an input properties file. The properties are converted to Tests Tags. For more information on Test Tags, see The Tag Data Store. |
| -junitDir | Indicates that JUnit reports are generated for all suites being run and the reports are placed in the specified folder. The default is to not generate reports. For more information on the format of the output file, see JUnit style output |
| -junitLegacy | Causes the junitDir option to behave as it did prior to Rational Integration Tester version 8.7.0. This earlier behavior requires junitDir to obtain information from the results database. |
| -license <key> | The license key key, if required, to use for running Rational Integration Tester. |
| -loginAsAdmin | Indicates to log in as the Administrator for a secured project. This requires the admin password to be specified using the -projectPass parameter. |
| -noHTTP | An optional switch to disable the internal web server. This switch must not be used when you are running performance tests. |
| -noDB | Causes test results to not be written to the results database, even when one is configured in the project. |
| -noResultsPublishers | An optional switch to disable any results publishers that can be configured in the project. |
| -overrideSlowFail | Overrides the slow fail setting in the root Scenario for a
Suite. The argument has the following values:
|
| -project <file> | The full path to the Rational Integration Tester project file <file> that contains the specified environment and test resources. |
| -parameterFile <file> | The full path to a parameter file that contains run options for one or more resources. For more information, see Using the parameter file in this topic. |
| -projectPass | The password for a secured project. |
| -projectUser | The user name for a secured project. |
| -resultsServerLogging absolute|relative|ignore | Specifies how the Results Server URL is written to the console
when tests complete. The argument has the following values:
|
| -run <res_1>;<res_2> | One or more resources to be run, separated with a semicolon.
A resource may be specified by any part of its name which will uniquely
identify it. You can also specify the internal resource ID instead
of resource name. Note: The internal resource ID field in the Documentation
tab of the resource represents the resource ID that can be used as
an alternative for the resource name.
|
| -securityToken <token> | Security token for authentication when domain security is enabled (optional). For more information, see Domain level security. |
| -useResultsPublishers <pub_1>,<pub_2> | One or more results publishers to be enabled for publishing. Each publisher is designated by the name that it was given when created in Rational Integration Tester. Multiple publishers must be separated by commas. |
You can set the project, environment, and run options in a parameter file, which you specify by using the parameterFile option.
You can specify the run options for one or more test resources, which are grouped by project and separated by a semicolon. As an example, consider a file that is named myparams.txt that has the following contents:
-project C:\Projects\AETesting\myproj.ghp -environment Env1 -run "creditTest1";"creditTest2";
-project C:\Projects\BWTesting\myproj.ghp -environment HotelApp -run "bookVisa;bookMaestro;reg Suite1;reg Suite2";You can use the parameter file in the RunTests command, as follows:
RunTests -noHTTP -resultsServerLogging ignore -parameterFile C:\RationalIntegrationTesterTests\myparams.txtIn the example file, the command runs the following resources: