Setting Test Execution Values

You can use the Execution pane in the Standard Values view to specify how tests in a test suite are run.

The Execution pane from the Configuration Editor: Standard Values view

Use the Execution pane to set:

Concurrency

The JavaTest harness can run tests concurrently. If you are running the tests on a multi-processor computer or are using multiple agents on a test system, concurrency can speed up your test runs. Refer to Using a JavaTest Agent for detailed information about using agents to run tests.

When using multiple agents to run tests, the concurrency value must not exceed the number of agents. If the concurrency value exceeds the total number of available agents, an error will occur in the test run.

If you have unexpected test failures, run the tests again, one at a time. Some test suites may not work correctly if you run tests concurrently.

For your first test run you should leave this field set to "1." After you have the tests running properly you can experiment with increasing this value.

Time Factor

To prevent a stalled test from stopping a test run, most test suites use a timeout limit for each test. The timeout limit is the amount of time that the JavaTest harness waits for a test to complete before moving on to the next test.

If you are running the tests on a particularly slow CPU or slow network, you can increase the time limit by specifying a value in the time factor field. Each test's timeout limit is multiplied by the time factor value.

Example:

If you specify a value of "2", the timeout limit for tests with a 10 minute basic time limit becomes 20 minutes.

Try running without a time factor first and increase the value as necessary.