6 Test Monitoring Document
For daily use consider a spreadsheet with the following tabs:
??? Document status
??? RFC (Request For Change) status
??? Test status
??? Log
??? Crash log
??? Raw bug reports
??? Weekly bug report count
??? Chart: test: execution status
??? Chart: overall bug detection profile
??? Chart: open and closed critical bug reports
??? Chart: release quality profile
8.6.1 Document Status
This lists the features and the specifications describing them, the authors of the specifications (aka
business analysts), the team leader in charge of developing that feature, the system tester in charge of
the feature, the document latest issue number, whether it had been reviewed by the system tester,
comments, its URL within the corporate intra-Web and whether it was signed-off. In this it is clear that
a number of documents should have been signed-off before testing started and may indicate last-minute
changes. Areas of concern can be colored.
8.6.2 RFC (Request for Change) Status
As testing progresses it may become evident that minor discrepancies between what the customer wants,
and what was specified and built have occurred. Reissuing the entire requirements specification may be very
FIGURE 8.13 Key to the preceding figure
FIGURE 8.14 Document status tab
STEP NAME STUB_SOFTWARE_NAME
MODULE _NAME
ANOTHER_
MODULE _NAME
Limit of a step
Relationship between a stub
and the modules it replaces
The integration
of two modules
INTEGRATED
_SOFTWARE
_NAME
Test Documents 143
long and involved.
Pages:
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324