FIGURE 8.28 Bug detection chart
Bugs by priorities
Time in days
Low
Medium
High
Critical
1
180
160
140
120 Numbers of bugs
100
80
60
40
20
0
3 5 7 9 11 13 15 17 19 21 23 25
162 Manage Software Testing
??? (Perhaps weekly) A chart showing which features were the primary sources of bugs.
??? A list of the headlines of the bugs found along with their priority and then name of the person
who found them (including a description of the impact on software and system performance, the
impact a correction would have on software and system design, and recommendations for correcting
the deficiency, limitation, or constraint).
??? An assessment of the software as demonstrated by the test results.
??? The percentage of tests completed (i.e., planned versus actual) taken from section 8.6.3.
??? The requirements coverage status (possibly using the test/feature matrix; see section 15.2 for an
example).
??? The documentation status: which specifications are available, reviewed, changes requested or
signed-off, and when.7
??? The RFC (Request For Change) status.
??? Any problems of the test environment for example taken from the Test log.
8.19 Reporting Using TestDirector?„? (now Quality Center)
We need to report daily on the status of test development and execution. One way is by using TestDirector
?„? (or its equivalent) and a primary spreadsheet. To populate this primary spreadsheet you need
to export a lot of test results from TestDirector?„? (now Quality Center) in Excel format.
Pages:
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349