This section describes the objectives and extent of the tests. The goal is to provide a framework that can be used by managers and testers to plan and execute the necessary tests in a timely and cost-effective manner.
1.1 Test objectives
The objective of the test suite is to provide adequate coverage metrics, requirements validation, and system quality data such that sufficient data is provided for those making the decision to release.
1.2 Extent of tests
The tests referenced herein are written to validate use cases, requirements (both functional and non-functional), system architecture, and object design. The structured tests for object design will be run first as the components of the system are developed. The structured tests to validate the system architecture will be run next as the system is integrated in bottom-up fashion during integration test.
2. Relationship to other documents
This section explains the relationship of the test plan to the other documents produced during the development effort such as the RAD, SDD, and ODD (Object Design Document). It explains how all the tests are related to the functional and nonfunctional requirements, as well as to the system design stated in the respective documents. If necessary, this section introduces a naming scheme to establish the correspondence between requirements and tests.
2.1 Relationships to documents
Black box tests relating to use cases are developed from the use case diagram(s) in the RAD (requirements analysis document).
Black box tests derived from functional requirements are developed from the requirements lists in the RAD.
Performance tests derived from nonfunctional requirements are developed from the nonfunctional requirements in the RAD.
Structured (unit/white box) tests are generated from the OOD (Object Design Document). The specific tests are developed from the OOD component diagram of each of the components.
Integration tests are...
Please join StudyMode to read the full document