1.3 Features to be tested
This section should identify all the features and combinations of
features that are to be tested. This may be done by referencing sections of
requirements or design documents.
References should be precise yet economical, e.g:
· 'the acceptance tests will cover all requirements in the User
Requirements Document except those identified in Section 1.4';
· 'the unit tests will cover all modules specified in the Detailed Design
Document except those modules listed in Section 1.4'.
Features should be grouped according to release number when
delivery is incremental.
1.4 Features not to be tested
This section should identify all the features and significant
combinations of features that are not to be tested, and why.
1.5 Approach
This section should specify the major activities, methods (e.g.
structured testing) and tools that are to be used to test the designated
groups of features.