TEST SPECIFICATION
1.0 Introduction
This section provides an overview of the entire test document. This document describes
both the test plan and the test procedure.
1.1 Goals and objectives
Overall goals and objectives of the test process are described.
1.2 Statement of scope
A description of the scope of software testing is developed. Functionality/
features/behavior to be tested is noted. In addition any functionality/features/
behavior that is not to be tested is also noted.
1.3 Major constraints
Any business, product line or technical constraints that will impact the mannerin
which the software is to be tested are noted here.
2.0 Test Plan
This section describes the overall testing strategy and the project management issues that
are required to properly execute effective tests.
2.1 Software (SCIís) to be tested
The software to be tested is identified by name. Exclusions are noted explicitly.
2.2 Testing strategy
The overall strategy for software testing is described.
2.2.1 Unit testing
The strategy for unit tested is described. This includes an indication of the
components that will undergo unit tests or the criteria to be used to select
components for unit test. Test cases are NOT included here.
2.2.2 Integration testing
The integration testing strategy is specified. This section includes a
discussion of the order of integration by software function. Test cases are
NOT included here.
2.2.3 Validation testing
The validation testing strategy is specified. This section includes a
discussion of the order of validation by software function. Test cases are
NOT included here.
2.2.4 High-order testing
The high-order testing strategy is specified. This section includes a
discussion of the types of high order tests to be conducted, the
responsibility for those tests. Test cases are NOT included here.
2.3 Testing resources and staffing
