3.17.2. Testing different AUTs in one test run
Prev | 3.17. Working with Test Jobs to test multiple AUTs | Next

### 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:

- The AUTs are either written with the same toolkit (e.g. Swing) or,

- you have specified your Project at the concrete level, and will only be testing areas of the AUTs that can be tested with the actions that are valid for all AUT types (i.e. no RCP-specific components are involved in the test) (Section 3.6.2, “Creating a new Project”).

- The AUTs are all defined in the same Project.

- The first AUT can either be started using the autrun command (Section 3.8.4.6, “Starting Java AUTs with the autrun command”) or via an AUT configuration (Section 3.8.1, “Configuring AUTs to be started from the ITE”). Any other AUTs required for the Test Job must have been started with the autrun command.

| 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:

- The AUT Agent must be running in lenient or non-strict mode (Section 3.2.2.3, “Starting the AUT Agent from the command line: options and parameters”).

- The AUTs must be written with the same toolkit (e.g. Swing) (Section 3.6.2, “Creating a new Project”).

- The AUTs have all been defined for this Project (Section 3.7, “Defining applications under test (AUTs)”).

- The order in which the launched AUTs will appear and be tested must be known.

  | When an AUT is launched by another AUT, the AUT ID for the new AUT is formed as AUT ID + 1. The next AUT to be started receives the ID AUT ID + 2, and so on. You can enter these AUT IDs in the Test Suites in the Test Job.

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.