Context
This phase begins when the testability review has been carried out on the test basis and the defects in it
have been processed as far as possible. The test specification runs in parallel with the completion of the software (or
parameterisation, in the case of packages). The software is the primary product of the development process and is
usually also on the critical path of the process. The focus of the (project) management is therefore upon this. The
test specification is only of indirect interest, but this changes at the point when the software is transferred for the
test execution and the attention of the (project) management is then drawn to it. The test team has to be ready then to
start the test execution. The test specification is aimed at preparing as much as possible so that the test execution
can be performed as fast as possible and be on the critical path for as short a period as possible. The test manager
has to be aware of this. He should translate, as far as possible, the signals given by the test specification problems
into consequences (in terms of time, finance and quality) for future test execution and the total productive process.
Preconditions
The following preconditions should be met before the Specification phase can be started:
-
The test basis is available and placed under configuration management
-
Defects from the testability review have been processed.
Method of operation
During the Specification phase, the testers specify the required tests per test unit. This is done by creating
checklists or specifying test cases on the basis of the allocated test design techniques. In the latter case, the
testers also create test scripts, in which the test cases are put into an efficiently executable sequence. On this
basis, and partly in parallel with it, the testers define one or more central starting points for the testing that the
test cases can use. This may be a copy of production or a central base table listing. A special form of a test to be
specified is the test object intake. This test should check in the Execution phase whether the test object is
sufficiently testable for a meaningful and efficient test execution.
Roles/responsibilities
The activities in the Specification phase are carried out by the testers.
Activities
Within the Specification phase, the following activities are distinguished:
-
Creating test specifications
-
Defining central starting point(s)
-
Specifying the test object intake.
The diagram below shows the sequence and the dependencies between the various activities. Activities 1 and 2 run in
parallel, but mutually influence each other.
Figure 1: Specification phase
|
