Context

The actual testing takes place during this phase. The test object is delivered and as much as possible has been prepared in the preceding phases in order to keep the test execution as brief as possible.

Preconditions

The following conditions should be met before the Execution phase can commence:

• The test object, or a separately testable part of the test object, should have been delivered.
• The test scripts for the test object, or the separately testable part of the test object, should be ready.
• The intake of the associated test infrastructure should have been completed successfully.

Method of operation

The actual execution of the test begins at the point when the test object, or a separately testable part of the test object, is delivered. The test object is first checked for completeness. Subsequently, it is installed in the test environment to assess whether it functions as it should. This is done by carrying out a preliminary test, the so-called pre-test. This is a general test, with the aim of examining whether the information system under test, in conjunction with the test infrastructure, is of sufficient quality to undergo extensive testing. If, on the whole, it is of sufficient quality, the central starting point is prepared. The test may be executed on the basis of the (manual or automated) test scripts that were created in the Specification phase. In that case, the starting points for the test scripts should first be prepared. Execution of the test can also be carried out in an exploratory manner, or on the basis of checklists. During the execution, the test results are logged. Investigation of the causes of any differences between expectations and obtained test results takes place after the test execution. Causes of differences may lie in software faults, but other causes are possible. For example, there could be mistakes in the test basis, in the test environment or in the test cases. When a fault has to be solved, this is formally reported as a defect. When the defect has been solved, a new test can be executed. Thus, this phase often involves an iterative process of test-rework-retest. The substance of this iterative process depends on the cause of the fault. For example, a fault in the test basis can result in a renewed (re)planning of the test, after which the phases of Preparation, Specification and Execution are gone through again. With a fault in the software, the iterative process of test-rework-retest may be restricted to a repeat of the Execution phase.

Roles / responsibilities

All the activities can be carried out by all the test-team members. However, the check on completeness of the test object is done by the test manager, aided by the (if applicable) test infrastructure coordinator.

Activities

Within the Execution phase, the following activities are distinguished:

1. Intake of the test object
2. Preparing the starting points
3. Executing the (re)tests
4. Checking and assessing the test results.

The following scheme shows the sequence and dependencies between the various activities.


Figure 1: Execution phase