Clearly
there is a large number of bugs still to be found.
62 Manage Software Testing
4.6.5 Release Readiness
Releases should not be made without your agreement. If a release isn??™t ready, you, the test manager must
be able to say ???no, that??™s not going out.??? Getting everyone to accept both this principle and the basis on
which it??™s established is one of the earliest battles you must win. If you are overridden by the project manager
(and you are after all acting for the project manager) then make sure it is clear that it??™s his responsibility.
A release is ready when:
??? All the tests have been run.
??? Test coverage is sufficient (see section 2.8 for more on this).
??? It has all the features required in it and they are stable (see Figure 8.25).
??? All the bugs needing to be fixed have been.
??? Code turmoil is low (see Chapter 18).
??? The reliability (see section 18.6.2) is satisfactory.
??? Testing has not revealed any more bugs of above some level of severity for some time.
??? The bug detection profile has flattened (see section 7.6.2 Bug tracking graphs in Chapter 7 for
more on this).
??? The expected number of bugs have been found (see section 18.10).
If this last bullet point sounds vague then remember that what matters is the risk the release poses. As
test manager you need to define what release risk means.
The chart in Figure 4.12 shows a project in which many bugs have been found in the past but which
is now quite stable and with few bugs being found in the last few days.
Pages:
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196