3.17.2. Testing different AUTs in one test run

You can test multiple AUTs in one test run.

The AUTs can be the same actual AUT which has been started multiple times (to test refresh aspects, for example).

You can test AUTs that were started independently, or AUTs that are launched by other AUTs.

3.17.2.1. Testing independently started AUTs

To be able to test multiple AUTs that are not started by each other, the following criteria must be met:

To run Test Jobs from the test executor, all AUTs for the test run must already be started when the test execution begins. For unattended build and test processes, this will mean that the AUTs must be started with the autrun command.

3.17.2.2. Testing AUTs that are launched by other AUTs

If your AUT starts other AUTs which you also want to test, then the following criteria must be met:

Behavior of AUTs when being started by other AUTs

RCP starting RCP:

The newly started RCP AUT receives the ID ID+1.

Swing Jar or main class starting Swing Jar or main class:

This is currently not possible.

Swing Jar or main class starting Swing executable:

This is currently not possible.

Swing executable starting Swing Jar or main class:

The newly started Swing AUT receives the ID ID+1.

Swing executable starting Swing executable:

The newly started Swing AUT receives the ID ID+1.

If the AUT Agent is not running in lenient mode, then the newly started AUT will shut down.



Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.