The number of bugs found is close enough to the number you expect to find. See section 18.10
.
2. All the tests have been run.
3. All the code has been exercised.
4. Every feature has been shown to work (with every other).
5. Every use case scenario has been exercised.
6. Code turmoil has fallen enough. See section 18.9.8
.
7. Feature stability is sufficient. See Figure 8.25.
8. The system can be shown to be within some Reliability, Availability, and Maintainability Profiles
defined in the test plan.
9. The number and severity of outstanding bugs has fallen to a satisfactory level.
10. When all regression, smoke, and confidence tests pass.
See section 8.5.9 for more on this.
Some projects are ???sticky??™; that is, no matter how much work you do there always seems to be more.
Having an exit criterion at least gives you a measure of how sticky the project is.
1.
An example:
management desperately wants to release v.1.0. It still has 8 priority-1 bugs unfixed,
to say nothing of the 50 priority-2s. Releasing it would probably cause severe problems for a
large number of customers, and perhaps bring down the company. But management is getting
hysterical. The Directors don??™t hear what management tells you and (unless you tell them) never
will. The Directors would be horrified if they ever understood the risks which management is
proposing to run.
Story
Note:
You will be punished for ???not starting system testing on time.
Pages:
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120