8.5.2 Introduction (Table 8.2)
8.5.3 Test Items
Specify the:
1. Test items including their version/revision level.
2. The characteristics of their transmittal media which affect hardware requirements or indicate the
need for logical or physical transformations before testing can begin (for example, that programs
should be transferred from tape to disk).
3. References to the following documents, if relevant:
a. Requirements specification
b. Design specification
c. User guide
d. Operations guide
e. Installation guide
4. References to any bug reports (from previous tests) relating to the test items.
5. Any items which are to be specifically excluded from testing.
TABLE 8.2
Boilerplate test plan introduction
Purpose of system testing
The purpose of the system test is to provide immediate feedback to the developers about:
??? Feature status
??? Release status
??? Possibility of release failure or delay
??? System performance
??? Any discrepancies between business and functional requirements and user interfaces
Scope of system testing
System testing:
??? Covers all issues of installation and use of all parts of the product
??? Includes the review of all business and functional requirements, and user interface specifications
??? Does not cover training, documentation, performance, or infrastructure testing
Criteria for seeking developer help in system testing
Given the difficulty experienced in getting features to work, it is essential that testers can call on help when necessary.
Pages:
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313