Definition and purpose

The purpose of ISO/IEC/IEEE 29119 is to define an internationally agreed set of standards for software testing that can be used by any organization involved in software development. It covers aspects such as test processes, test documentation, test techniques, and test management, aiming to provide a comprehensive guide for effective and efficient software testing.

Governing Body

The standard is developed and maintained by the International Organization for Standardization (ISO), the International Electrotechnical Commission (IEC), and the Institute of Electrical and Electronics Engineers (IEEE). 

Last updated

• Part 1: Published in 2013, updated in 2022. 
• Part 2: Published in 2013, updated in 2021. 
• Part 3: Published in 2013, updated in 2021. 
• Part 4: Published in 2015, update in 2021.

Applies to

ISO/IEC/IEEE 29119 is applicable to any organization engaged in software development, including software developers, test engineers, quality assurance professionals, project managers, and any other stakeholders involved in the software development lifecycle.

Controls and requirements

ISO/IEC/IEEE 29119 is divided into several parts, each focusing on different aspects of software testing:

• ISO/IEC 29119-1: Specifies definitions and concepts.
• ISO/IEC 29119-2: Covers the organizational test processes, including test planning, design, execution, and evaluation.
• ISO/IEC 29119-3: Focuses on test documentation, including test plans, test designs, test cases, test procedures, and test reports.
• ISO/IEC 29119-4: Details test techniques, including black-box testing, white-box testing, and experience-based testing.
• ISO/IEC 29119-5: Addresses risk-based testing processes.

Please refer to the official ISO/IEC/IEEE 29119 documentation for details on controls and requirements.

Audit type, frequency, and duration

Audits for ISO/IEC 29119 compliance typically involve assessing the organization's software testing processes and documentation against the standard's requirements. The frequency of such audits can be based on the organization's internal audit schedule, regulatory requirements, or when significant changes are made to the testing processes or the software being tested.

The duration of an audit depends on the size and complexity of the organization's software development and testing operations.