Additions to User Interface requirements are excluded from consideration on the
grounds that they only concern usability. Any additional feature is expected to be introduced only through a business
requirement. System testing will therefore halt when:
??? Any change or addition to any business requirement (for the period required to redefine the functional requirements,
add those requirements to the tests, and examine any knock-on effects such (an) addition(s) may have), is made
??? Any changes (as opposed to additions) to four or more functional requirements (for the period required to examine
and make the changes to the tests those changes imply) are made
??? More than 50 percent of the proposed functionality as defined in the business requirements cannot be executed
FIGURE 8.5
Alternative boilerplate test plan specification of suspension criteria (severity)
Example:
Testing will be discontinued on any build if one of the following conditions is encountered:
??? 2 severity 1 bugs found,
??? 3 severity 2 bugs found,
??? 8 priority 3 bugs found.
Testing will not be halted if any lower-severity bug is found. Testing will resume when a new release is available.
The test execution order will then be:
??? Smoke and con?¬?dence tests.
??? The tests which found the bugs which have just been ?¬?xed.
??? The regression tests.
??? The rest of the tests.
Test Documents
137
If the system tests are to be used for acceptance or certification purposes, this section should also define:
??? The procedures for agreeing the success of individual tests.
Pages:
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317