What is ISO/IEC/IEEE 29119‑3 about?  
 ISO/IEC/IEEE 29119‑3 specifies software test documentation templates that can be used for any organization, project, or testing activity. ISO/IEC/IEEE 29119‑3 describes the test documentation that is an output of the processes specified in ISO/IEC/IEEE 291192.
ISO/IEC/IEEE 29119‑3 is applicable to testing in all software development lifecycle models.
Note: ISO/IEC/IEEE 29119‑3 is intended for, but not limited to, testers, test managers, developers, and project managers, particularly those responsible for governing, managing, and implementing software testing. 
 Who is ISO/IEC/IEEE 29119‑3 for? 
 ISO/IEC/IEEE 29119‑3 on software testing is useful for: 
- Software developers
- Software testers
- Software debuggers
- Project managers
- Stakeholders of the company
Why should you use ISO/IEC/IEEE 29119‑3?  
Test documentation helps the organization in document test planning, test design, test execution, test results that are drawn from the testing activity.
ISO/IEC/IEEE 29119 aims to provide stakeholders with the ability to manage and perform software testing in any organization. ISO/IEC/IEEE 29119‑3 can be adopted under any lifecycle methodology including traditional (e.g., waterfall, iterative), agile or DevOps.  
ISO/IEC/IEEE 29119 defines templates and provides examples of test documentation that are produced during the test process. The test documentation described in ISO/IEC/IEEE 29119 can be on paper or in electronic form (e.g., records in test tools, spreadsheets, mind maps, whiteboard photos).
ISO/IEC/IEEE 29119 uses the traditional concept of organizations and projects, but some organizations, especially those using an agile approach, do not organize their development in terms of projects; instead, they run product development based on more long-lasting product teams. Users of ISO/IEC/IEEE 29119‑3 can substitute the term ‘product’ for ‘project’, where appropriate.
What’s changed since the last update? 
ISO/IEC/IEEE 291193:2021 supersedes BS ISO/IEC/IEEE 291193:2013, which is withdrawn.
 The main change compared to the previous edition is that the concept of test conditions has been replaced by test models, as feedback on the previous edition of this document highlighted a problem with users’ understanding of ‘test conditions’ and their use for deriving test cases.
