12 for details of how to prepare one)
f. Enter any bugs you find in the bug management tool (see section C.2 in Appendix C for advice
on documentation bugs). Don??™t be persuaded that these aren??™t real bugs by the developers or
management.
3
Knowing how many bugs you found in each phase (and indeed each document)
is critical for predicting bug totals. And if the bugs aren??™t recorded how can you be sure they??™ll
be fixed?
8.
Plan and specify
(in outline)
the system tests:
a. Identify a subset of the system tests for smoke test purposes
b. Identify a subset of the system tests for regression test purposes
4
c. Identify another subset of the system tests for system test dry-run purposes
d. Identify and add any tests required for customer acceptance if not yet included
9.
Review the tests
. See section B.7 in Appendix B.
10.
Design, code, or acquire the test tools.
It may seem better to wait to do this until unit design has
begun but there won??™t be enough time then.
Probably a few of these details will not exist at the time you are planning, and their absence will come
as a warning to both you and the project manager.
3
???
I don??™t feel these issues are best placed in the defect management database
??? was one attempt, swiftly demolished
by asking where else they would go and how they should be tracked.
4
Regression and smoke testing answer different questions. Smoke tests simply say ???
It??™s worth testing this build
??? (or
not) and need to be short.
Pages:
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237