4 in Chapter 4. The following sections identify the test-related activities that should occur irrespective
of the life-cycle adopted. As with all processes it is necessary that they are clear to the staff engaged in
them. The following description is simplified in that the phases described will normally overlap one
another and may be simultaneous.
6.1 Initiation Phase
This is the period, before the project starts, when the system is first identified, perhaps as part of some
future component or as a stand-alone.
??? If possible,
review the tender or the contract
to see what testing commitments have been made.
??? Undertake a
sizing exercise
to get some sense of how many tests you must write. Note section
18.12 in Chapter 18.
???
Identify the configuration management
and change control processes to be applied to all documents.
Note that if your requirements specifications derive from such other documents as business
process models or system specifications, then you need to track changes to these documents as
well if you are going to modify your tests in a timely manner.
1
The exception is, of course, the test automation process.
2
Start again generating the next version (and fixing this version??™s bugs which were found in the field).
84
Manage Software Testing
??? Draft a
test strategy document
as described in section 8.3 in Chapter 8. Use this to identify what
is exceptional about this project before getting into the detail of test planning.
Pages:
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232