5).
2. A number of bugs of a certain category being found (see Figure 8.6 through 8.8).
A list of priorities and categories can be found in Appendix C. This section is proposed only for formal
system test plans. See Chapter 18.
136
Manage Software Testing
TABLE 8.3
Boilerplate test plan specification of suspension criteria
Criteria for system test start
For system testing to begin the following criteria must be met:
??? A signed-off system test review report of the baseline specifications (business and functional requirements) for that release exists
??? A test plan for that set of tests has been approved by the test and project managers
??? All server-side configuration issues are resolved
??? All tests have been specified, and manual or automated test scripts are prepared
??? Every requirement is matched by at least one test
??? Any extra tools needed for test execution are defined, procured, installed, and working
??? A smoke test covering the key features of that release has been run on a machine outside the system test environment,
without any unacceptable failures occurring
??? A confidence test has been run with 70% of the tests passing
??? A release note explaining known weak points or unfixed bugs exists
Criteria for system test interruption
??? Releases collapse. Some releases may appear good, but a day or so of testing reveals major flaws.
??? Changes happen. Some need to be accounted for. No addition to a functional requirement is assumed to occur without a
corresponding business requirement.
Pages:
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316