Run tests by using the command line
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. An example follows:
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. An example follows:
RunTests [-licence key] [-noHTTP] [-noResultsPublishers]
[-useResultsPublishers pub_1,pub_2] [-resultsServerLogging absolute|relative|ignore]
-parameterFile file
For 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 you run 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.
|
-environmentTags env | All environment variables are available as environment tags,
overriding any existing environment tags with the same name. Note: If
you also specify -input, the properties for that argument take precedence
when Rational Integration Tester resolves
an environment tag value.
|
-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 that are 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 argument to behave as it did before 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 option requires the admin password to be specified by 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. |
-output | Allows the list of tags present in the executed test, which were marked with a type of output to be written to the specified file. The contents are structured according to the Java properties file format as used by the -input argument. |
-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 arguments for one or more resources. For more information, see Using the parameter file. |
-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 can be specified by any part of its name, which uniquely
identifies 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. |
Using the parameter file
You can set the project, environment, and run arguments in a parameter file, which you specify by using the parameterFile argument.
You can specify the run arguments 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.txt
In the example file, the command runs the following resources:
- In the AETesting project, creditTest1 resources are run followed by creditTest2, and both are run in the Env1 environment.
- Next, in the BWTesting project and by using the HotelApp environment, bookVisa, bookMaestro, reg Suite1, and reg Suite2 resources are run (in that order).
Checking the test status
- On Windows systems, echo %errorlevel%
- On systems other than Windows, echo $?