Prev | Current Page 115 | Next

Peter Farrell-Vinay

"Manage Software Testing"

And yes, maybe if we??™d been more thorough we??™d have found that bug earlier.
Circulate a spreadsheet like the one shown in Table 2.2.
TABLE 2.2
Late-found bug list
SCR No. Headline Tester Date raised Severity Outcome Why not found earlier
7690 Text Editor:
Intermittent error
and unable to
shutdown
NewSystem
Feroza 03.11.04 High May be Critical.
Being monitored. If
not will be moved to
Callisto
Ad hoc test
7738 Notes Editor??”TAB
button does nothing
Mat 04.11.04 Medium Intermittent problem.
Test has been produced
after the Minor
Transactions UI spec
(which required all
Notes Editor UI tests to
need rewriting).
7708 Schedules??”Pasting
of bulleting lists has
XML appear in the
TextEditor
Schedules??”Pasting
of numbered lists
has XML appear in
the TextEditor
Mat 04.11.04 High TextEditor Shortcuts Passed in Drop 21.
Found while executing
this test but not as a
result of it.
Passed in Drop 21.
Found while executing
this test but not as a
result of it.
24
Manage Software Testing
Just having the list and having already got the answers from the testers will help you both bat back some
criticisms and give you better insights into how tests should be managed.
2.7.2 How Many Bugs Are Being Introduced with Each Fix?
Microsoft suffered from this problem in the 1980s. It is called the
infinite defect loop
. It caused major
delays to their development of Windows 3.0. The WinWord project took five years, starting in 1983, and
was delayed for the same reason.


Pages:
103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127