These are discussed in Chapter 18. Review the test plan with the project manager.
??? Write a
process model
of how you are going to test the software and what items (documents,
code, tests, reports, etc.) will pass between the stakeholders and you. Show in particular how you
will interface with developers, configuration management, project management, external suppliers,
and the customer. Show all the support systems you will need such as:
??“ A bug management tool (at its simplest this can be an Access database) to record the bug
reports and display the quantity and type found to date (see section 7.6)
??“ A configuration management tool to manage the test specifications and software (if your
organization doesn??™t have a suitable one already)
??“ Test harnesses and test management software
??“ Test automation software
??? Identify, evaluate, and obtain what you need. Put it under configuration management.
6.2 Requirements Analysis Phase
The software requirements specification forms the baseline of the system tests. Writing it will permit
much of the detail of the system-test phase of the software test plan to be completed and allow those
responsible for the system testing to begin specifying the system tests. During this phase:
1.
Review the requirements specifications.
They may be all you will ever be given to define the
features you must test. If you are using automated test tools you will need to be sure that the
requirements specifications contain enough detail to allow testers to manually-test the system
before they start preparing them.
Pages:
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234