Software and systems engineering — Software testing — Part 3: Test documentation
Introduction: The purpose of ISO/IEC/IEEE 29119 (all parts) is to define an internationally-agreed set of standards for software testing that can be used by any organization when performing any form of software testing. ISO/IEC/IEEE 29119-1 introduces software testing concepts. This document uses the concepts of ISO/ IEC/IEEE 29119-1. ISO/IEC/IEEE 29119-2 comprises test process descriptions that define the software testing processes at the organisational level, test management level and dynamic test levels. It supports dynamic testing, functional and non-functional testing, manual and automated testing and scripted and unscripted testing, and can be utilized within any lifecycle model, including agile and traditional methodologies. Supporting diagrams describing the processes are also provided. ISO/IEC/IEEE 29119-4 defines software test design techniques, which can be used within any lifecycle and for any product. ISO/IEC/IEEE 29119-5 addresses the use of keyword-driven testing. This document defines templates and provides examples of test documentation that are produced during the test process. An overview of the test documentation is provided in Figure 1. The templates are arranged within clauses reflecting the overall test process description structure in ISO/IEC/ IEEE 29119-2, i.e. by the test process in which they are being produced. Annex A contains a list of all the information items identified in Clauses 6, 7 and 8 with the corresponding level of conformance (shall/ should/may) fro
Scope: This document specifies software test documentation templates that can be used for any organization, project or testing activity. It describes the test documentation that is an output of the processes specified in ISO/IEC/IEEE 29119-2. This document is applicable to testing in all software development lifecycle models. This document is intended for, but not limited to, testers, test managers, developers, and project managers, particularly those responsible for governing, managing, and implementing software testing.