3.16.2. Configuring Test Suites in the Properties View
Prev | 3.16. Working with Test Suites | Next

### 3.16.2. Configuring Test Suites in the Properties View

To configure a Test Suite, you must first create one (Section 3.16.1, “Creating a Test Suite”).

1. Open the Test Suite Editor by double-clicking on the Test Suite you want to configure.

2. In the Properties View, you can:

   1. Change the Test Suite name by entering a new name in the Test Suite name field.

   2. Add a comment to the Test Suite (Section 3.10.7, “Adding comments to items in editors”).

   3. Enter a value in the step delay field. The step delay is the time left between each Test Step during test execution. The default is 0 milliseconds (Section 3.21.5, “Altering the speed of test execution”).

   4. Enter a Task ID to link this Test Suite to a task in an external system (Section 3.24.5.3, “Adding task IDs to Test Suites and Test Cases”).

   5. Set whether this Test Suite should be relevant or not. If a Test Suite is marked as non-relevant, test results for this Test Suite are created but are not exported with the Project, are not considered for any BIRT reports (Section 3.23.1, “Generating BIRT reports”)and do not save details to be reported to external ALM repositories (Section 3.24.5, “Automatically reporting to external repositories after test runs”).

   6. Select the AUT for this Test Suite. To be able to select an AUT (and object map, and execute your test) you must have added at least one AUT to the Project (Section 3.7, “Defining applications under test (AUTs)”).

      | You don’t have to choose an AUT for a Test Suite as soon as you have created it, but you will have to choose one before object mapping, for example.

   7. Choose a default reentry type for each of the four error types from the combo-boxes.

      Event Handlers are Test Cases used to deal with errors during test execution. When an error occurs, the current Test Case is searched for an Event Handler for that error type. If none is found, the parent Test Case is searched, and so on. If no Event Handler for the test is found, then a default Event Handler (specified in the Test Suite properties)is activated.

      As a general rule, you should avoid default Event Handlers being executed. See the sections on Event Handlers for information on the event types (Section 3.27.3, “Event types”), reentry types (Section 3.27.4, “Reentry types”) and creating your own Event Handlers.

   8. Save the changes in the Test Suite Editor.