2. Overall bug detection profile (Figure 8.21). This shows the overall number of bug reports raised
against a release. The shape roughly corresponds to the expected ???S??? curve. The profile looks as
if the number of bugs is at last beginning to drop and the release can soon be made.
3. Open and closed critical bug reports. The project had four bug report severity levels: Critical,
High, Medium, and Low. Critical implied some feature was missing or didn??™t work, and there was
no workaround. High implied there was a workaround. The software was not fit for release if any
of these bug reports remained. Therefore monitoring them was most important. As in Figure 8.22,
the profile has assumed an ???S??? shape. All ???allegedly-fixed??? bug reports have been retested and have
either been closed or rejected. A worryingly-high number (174) of open bug reports remains.
4. Build quality profile. Figure 8.23 shows the number of bug reports raised against each build.
Release 6 had only one bug report but it was so critical the release was abandoned. Thereafter the
bug profile has fluctuated.
FIGURE 8.20 Test execution status
1 Strictly speaking tests only ???fail??? if they fail to expose a bug they should expose. Software fails or passes. References
to tests ???failing??? means only that they exposed a bug. Tests never pass: only software passes, references to tests ???passing???
means only that they failed to expose a bug.
Pages:
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327