By now it is known why testing is
being done and what shall be tested has been also agreed. In this section one
would now outline the activities that need to be carried out to meet the test
objectives based on the test components. This is the necessary thinking process
that testers should go through to ensure that all system aspects are being
addressed. One would need to think of the normal and abnormal lives of data and
functions. The "#" column is self-explanatory. The "Activities" column is where
the test activities are captured and outlined.
The "When" column is where the
date or dates (from - to) are entered. The "Who" column is where the name or
initials of the individual or individuals are captured. This means that although
in the test script header, only one tester is listed, a test script could be
assigned to one or more testers. The column "T/B Ref" is to enable the mapping
of any task activities to the relevant timebox plan. This is not necessary a one
to one mapping. It is acceptable to have many tasks in the Test Script mapped to
one activity in the Timebox plan. The example below, line 1 indicated that, that
given task will be done on the 13/02/2000 by John Smith and it is mapped to
timebox CS02 Investigation Iteration Line 3.
Example
------->
Prepare the transaction at location A to be pulled from location
B---->13/02/2000----->JS----CS02/I3
------->
Prepare the test database for the extrapolation process
update------->14/02/2000------>CB---CS02/I3