An overall plan for integration of the software and a description of specific tests are documented in a test specification. The specification is deliverable in the software engineering process and becomes part of the software configuration.

Test Specification Outline

1. Scope of testing
2. Test Plan
3. Test phases and builds
4. Schedule
5. Overhead software
6. Environment and resources
7. Test Procedures
8. Order of integration
9. Purpose
10. Modules to be tested
11. Unit test for modules in build
12. Description of test for module n
13. Overhead software description
14. Expected results
15. Test environment
16. Special tools or techniques
17. Overhead software description
18. Test case data
19. Expected results for build
20. Actual Test Results
21. References
22. VI. Appendices

The Following criteria and corresponding tests are applied for all test phases.

1. Interfaces integrity. Internal and external interfaces are tested as each module is incorporated into the structure.
2. Functional Validity. Tests designed to uncover functional error are conducted.
3. Information content. Tests designed to uncover errors associated with local or global data structures are conducted.
4. Performance Test designed to verify performance bounds established during software design are conducted.

A schedule for integration, overhead software, and related topics are also discussed as part of the “test Plan” section. Start and end dates for each phase are established and availability windows for unit tested modules are defined. A brief description of overhead software(stubs and drivers) concentrates on characteristics that might require special effort. Finally, test environments and resources are described.

RELATED POST

INTEGRATION TESTING PART TWO