3.7. Defining applications under test (AUTs)
Prev | Chapter 3. Tasks | Next

## 3.7. Defining applications under test (AUTs)

Once you have created a Project, you can define (and edit) AUTs. You can define a new AUT straight after creating the Project in the Project wizard or you can do it later on via the Project properties (Section 3.6.3, “Editing the Project and AUT properties”).

| If you will be starting your Java AUT with the autrun command (Section 3.8.4.6, “Starting Java AUTs with the autrun command”), then you can automatically define your AUT (Section 3.8.4.7, “Creating an AUT definition from a running AUT”)

The AUT dialog (Figure 3.12, “AUT Dialog”) appears when you define or edit an AUT.

Figure 3.12. AUT Dialog

If you know that you will be working with multiple versions of the same AUT (e.g. a version for Windows and Linux, or two versions that use different databases), then define one AUT here and create multiple configurations (Section 3.8.1, “Configuring AUTs to be started from the ITE”) for this AUT. This means that your different configurations will all share one object map. If you are working with multiple completely different AUTs, then define the different AUTs here.

1. Enter a meaningful and unique AUT name. This is used to easily identify the AUT later.

2. Select the toolkit the AUT uses from the combo box.

3. If you choose RCP, decide whether or not you want to generate names for components in the AUT which have not been named by your developers (Section 4.3.6, “Component name generation in RCP”). We recommend leaving this option checked, as it increases the robustness of your tests.

4. If you are starting a Java AUT and will be starting it using the autrun command (Section 3.8.4.6, “Starting Java AUTs with the autrun command”), or if the AUT will be launched from another AUT during the test (Section 3.17.2.2, “Testing AUTs that are launched by other AUTs”), then enter the ID(s) for these AUTs here.

   IDs for AUTs started by the autrun command
   Enter the AUT IDs you will use for any AUTs started by the autrun command (the AUT ID for the AUT is given as a parameter in the autrun command (Section 3.8.4.6, “Starting Java AUTs with the autrun command”).

   IDs for AUTs launched by other AUTs
   The AUT ID will take a specific form (Section 3.17.2.2, “Testing AUTs that are launched by other AUTs”) and must be defined as such in the AUT definition.

   | If you will be starting your AUT from the ITE (i.e. via an AUT configuration (Section 3.8.1, “Configuring AUTs to be started from the ITE”)) then you do not need to enter any IDs here.

5. If you want to start this AUT from the ITE, you can do so in the Project properties (Section 3.8.1, “Configuring AUTs to be started from the ITE”).

6. If you need to configure how your AUT is handled by Jubula, you can add properties to the AUT property table. For example you can use timeout to specify a timeout (in milliseconds) for connecting to your AUT.

If you do not require an AUT configuration, because you will be starting the AUT using the autrun command (Section 3.8.4.6, “Starting Java AUTs with the autrun command”), then you do not need to create an AUT configuration.