5.05 - Execute an iteration/test suite

The test execution phase is made from the Test plan tab in the iteration consultation page.

5.5.1 Execution consultation page

The information of an execution can be consulted by clicking on the name of a test case in the Test plan tab table. The execution consultation page opens and displays six information toggle panels and a toolbar.

Note: The Execution consultation page will be different in the case of a Gherkin or BDD test case.

5.5.2 Launch a manual execution

Prerequisite: A campaign/iteration/test suite is created and test cases are associated with it.

1. Click on the name of the test case to execute in the test plan tab table.

2. Click on [New execution]. The execution consultation page opens.

3. In the execution consultation page, there are two ways to run an execution:

   • Click on [Execute]. A pop-up window opens with the step 0 of the test case to execute.

   • Click on [Run with OER]. The OER interface opens with the step 0 of the test case to execute.

4. Click on [Begin].

Or:

1. Click on [Start an execution] at the end of the line

2. Choose between [With pop-up] or [With OER]

3. The execution pop-up window opens.

4. Click on [Begin].

5.5.2.1 Pop-up window Execution details

5.5.2.2 OER Execution details

5.5.3 Execute steps

The user has two procedures to run the step execution:

a. Use the shortcuts [Untestable], [Blocked], [Failure] or [Success] .

The statuses Untestable, Blocked, Failure or Success are tied up to the step and the following step runs automatically. By clicking on the shortcuts for the last step, a tooltip opens, announcing the end of the test. Click on [Ok], the user comes back on the execution consultation page.

b. Use the drop down status menu to assign one of the five statuses to the running step.

To pass to the following step, it is necessary to use the step navigation buttons. If the user chooses the drop down menu for the last step status, then he will have to click on the [Break off] button to end the execution.

The Execution script unit is refreshed after each step.

Note : 'Untestable' and 'Settled' status will be affected to the running execution only if they are accepted in the Project Workspace by the administrator.

5.5.3.1 Suspend an execution

It is possible to suspend a running execution by clicking on [Off] (symbolized by a switch icon). The execution running is stopped on the last executed step and the execution pop-up window or the OER interface shuts itself.

The user is sent back to the execution consultation page.

The status « Running » is affected to the execution.

5.5.3.2 Run once again the execution

The interrupted execution can be run once again from the consultation page by clicking on [Resume].

5.5.4 Assign test cases to a user in a campaign/iteration/test suite

It is possible to assign an execution to a specific user from the test plan tab of a campaign/iteration/test suite.

5.5.4.1 Simple assignation

In a campaign/iteration test plan, the "User" column proposes a combo box.

The user has the choice between:

• • Unassigned

  • The list of the user having an accreditation on the project

After the user's choice, the "User" column is refreshed.

FOCUS

From 1.20, the first name, the last name and the login is displayed in the user column.

5.5.4.2 Multiple assignation

1. Select the test cases in the test plan of a campaign/iteration by clicking on their sequence number.

2. Click on [Assign]. A pop-up window opens with a combo box. Select one of these choice :

   1. • Unassigned

      • The list of the user having an accreditation on the project

3. Click on [Assign], the "User" column of the test plan is refreshed.