2. Is only available when it is no longer useful, some months after the release.
An alternative is to:
1. Identify a series of indicators (number of bugs found by testers as a proportion of the whole,
average number of bugs found per day, total number of bugs found as a proportion of estimated
bugs found, priority-1s and priority-2s as a proportion of all bugs found).
2. Compare them with previous releases and observe the fluctuations.
3. Use a bug-seeding tool to estimate how many bugs remain in the system (when enough of the
system has automated tests written).
See also section 2.7.2 and section 18.10.2.2.
2.7.1 Why Didn??™t We Find That Bug Earlier?
This is a cry frequently heard as deadlines approach. There could be a number of answers:
1. The testers were not able to complete testing due to a new release being loaded.
2. The bug was not in an earlier release (reload that earlier release and see).
3. The bug could not be tested for earlier because some part of the release did not work and inhibited
the test??™s ability to ???see??? the bug.
4. The bug was in some part of the system not originally planned for the release for which a test has
only just been written.
5. The bug was found while running some other test.
6. The bug was in a part of a system which was not the focus of testing.
7. The bug would have been found eventually, but the tester hadn??™t run the test (which would have
found it) yet.
8.
Pages:
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126