Context
With the structured test approach of TMap, much benefit is to be gained from the possibility of repeating the
process. This allows products, provided that they meet certain requirements, to be reused in a subsequent test. In
turn, this can ensure that certain activities will proceed faster. Products may be tangible things, such as test cases
or test environments, but also intangible things, such as valuable experience.
Preconditions
The following condition should be met before the Completion phase can commence: The test execution is almost
finished.
Method of operation
The test process is evaluated. The aim here is to learn from the experience gained and to apply the points of
learning to any new test. This also serves as input for the final report, which the test manager creates in the Control
phase. Also a selection is made from the often large quantity of testware, such as the test cases and the description
of the test infrastructure. The point here is that with changes and associated maintenance tests, the testware only
requires adjustment, so that it is not necessary to design a completely new test. During the test process, efforts are
made to keep the test cases corresponding with the test basis and the developed system. If necessary, the selected
test cases should be updated.
Roles / responsibilities
All the activities can be carried out by all the team members.
Activities
The Completion phase consists of the following activities:
-
Evaluating the test process
-
Preserving the testware.
The scheme below shows the sequence and dependencies between the various activities:
Figure 1: Completion phase
|
