The following lists the batch commands used to set Standard Values in the current configuration:
concurrency
Use the concurrency
command to specify the number of tests to run concurrently:
concurrency number
If you are running the tests on a multi-processor computer, you can use concurrency to speed up your test runs. Unless your test suite restricts concurrency, the maximum number of threads specified by the concurrency
command is 50. See your test suite documentation for additional information about using concurrency values greater than 1.
Example:
...;concurrency 2;
...
env
Use the env
command to specify a test environment in an environment file:
env environment-name
This is only used with envFiles
of test suites that use parameter (.jtp) and environment (.jte) files.
Example:
...;env testsystem;
...
envFile
Use the envFile
command to specify an environment file (.jte) containing test environments that the JavaTest harness uses to run older test suites:
envFile file-name
The environment file is not used by newer test suites that use a configuration (.jti) file.
Example:
...;envFile test.jte;
...
excludeList
Use the excludeList
command to specify one or more exclude list files containing a list of tests that are not to be run:
excludeList file-name
Exclude list files conventionally use a .jtx extension and are normally supplied with a test suite.
Example:
...;excludeList sample.jtx;
...
keywords
Use the keywords
command to restrict the set of tests to be run based on keywords associated with tests in the test suite:
keywords expression
Refer to the test suite documentation for a list of keywords that are supported.
Example:
...;keywords interactive;
...
params
These commands are deprecated. However, for backwards compatibility, if you are running a test suite that uses a parameter file (.jtp
) you can continue to use the params
command and its arguments to set parameter values when starting the JavaTest harness. Refer to Use of Parameter Commands for detailed information about using the params
command.
priorStatus
Use the keywords
command to select the tests for a test run based on their outcome on a prior test run:
priorStatus status-arguments
The status-arguments that can be used are "pass," "fail," "error," and "notRun." If you use more than one argument, each argument must be separated by a comma.
Example:
...;priorStatus fail,error;
...
tests
Use the tests
command to create a list of test directories and/or tests to run:
tests test-name
The JavaTest harness walks the test tree starting with the sub-branches and/or tests you specify and then executes all tests that it finds (unless they are filtered out).
Example:
...;tests api;
...
timeoutFactor
Use the tests
command to increase the amount of time that the JavaTest harness waits for a test to complete before moving on to the next test:
timeoutFactor number
Each test's timeout limit is multiplied by the time factor value. For example, if you specify a value of "2", the timeout limit for tests with a 10 basic time limit becomes 20 minutes.
Example:
...;timeoutFactor 2;
...