Table of Contents
3 Test Plan
4 Test-Design Specification
5 Test-Case Specification
6 Test-Procedure Specification
7 Test-Item Transmittal Report
8 Test Log
9 Test-Incident Report
10 Test-Summary Report
Appendix A - Examples
Appendix B - Implementation and Usage Guidelines
Appendix D - Annotated Bibliography
Describes a set of basic test documents which are associated with the dynamic aspects of software testing (i.e., the execution of procedures and code). This Standard is identical with and reproduced from ANSI/IEEE Std 829-1983.
This standard describes a set of basic test documents which are associated with the dynamic aspects of software testing (that is, the execution of procedures and code). The standard defines the purpose, outline, and content of each basic document. While the documents described in the standard focus on dynamic testing, several of them may be applicable to other testing activities (for example, the test plan and test incident report may be used for design and code reviews). The standard may be applied to commercial, scientific, or military software which runs on any digital computer. Applicability is not restricted by the size, complexity, or criticality of the software. However, the standard does not specify any class of software to which it must be applied. The standard addresses the
documentation of both initial development testing and the testing of subsequent software releases. For a particular software release, it may be applied to all phases of testing from module testing through user acceptance. However, since all of the basic test documents may not be useful in each test phase, the particular documents to be used in a phase are not specified. Each organization using the standard will need to
specify the classes of software to which it applies and the specific documents required for a particular test phase.
The standard does not call for specific testing methodologies, approaches, techniques, facilities, or tools, and does not specify the documentation of their use. Additional test documentation may be required (for example, code inspection checklists and reports). The standard also does not imply or impose specific methodologies for
documentation control, configuration management, or quality assurance. Additional documentation (for example, a quality assurance plan) may be needed depending on the particular methodologies used. Within each standard document, the content of each section (that is, the text which covers the designated topics) may be tailored to the particular application and the particular testing phase. In addition to tailoring content, additional documents may be added to the basic set, additional sections may be added to any document and additional content to any section. It may be useful to organize some of the sections into subsections. Some or all of the contents of a section may be contained in another document which is then referenced. Each organization using the standard should specify additional content requirements and conventions in order to reflect their own particular methodologies, approaches, facilities, and tools for testing, documentation control, configuration management, and quality assurance. The standard applies to documentation on electronic media as well as paper. Paper must be used for documents requiring approval signatures, unless the electronic documentation system has a secure approval annotation mechanism and that mechanism is used.
First published as AS 4006-1992.