Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
BS ISO/IEC/IEEE 29119 — Software Testing Series (Concepts, Processes, and Documentation)
Software and systems engineering — Software testing (ISO/IEC/IEEE 29119 series)
🧪 BS ISO/IEC/IEEE 29119 is the UK implementation, published by the British Standards Institution (BSI), of the ISO/IEC/IEEE 29119 international series, which specifies Software and systems engineering — Software testing. Prepared under the responsibility of BSI Technical Committee IST/15 (Software and systems engineering), it supersedes the withdrawn BS 7925-1:1998 and provides unified concepts, processes, documentation, and technical requirements for software testing. It is a widely referenced international standard in software quality assurance and test management.
💡 29119 is often called “the constitution of software testing”. It does not prescribe a particular test tool or technique, but clarifies “what testing does, how the process runs, and how documents are written”, enabling horizontal comparison and improvement of test practice across teams and organizations.
1. Series Overview and Background 📌
Software testing long lacked unified international terminology and process standards, making test activities hard to measure and compare. The ISO/IEC/IEEE 29119 series was jointly developed by ISO, IEC, and IEEE, and its parts began publishing in 2013. BSI implemented it as British Standards, forming the BS ISO/IEC/IEEE 29119 series and superseding the older BS 7925 software-testing terminology standard.
The parts progress from basics to specifics: Part 1 defines concepts and definitions, Part 2 defines test processes, Part 3 defines test documentation, and Parts 4 and 5 further specify test techniques and keyword-driven testing methods.
⚠️ In this batch, BS ISO/IEC/IEEE 29119-4:2015 and BS ISO/IEC/IEEE 29119-5:2016 are scanned editions; their content here is summarized from public domain knowledge. Always refer to the official BSI published version for exact clauses.
2. Series Structure and Technical Highlights 📋
| Standard | Part Title | Year | Key Technical Content |
|---|---|---|---|
| BS ISO/IEC/IEEE 29119-1:2013 | Concepts and definitions | 2013 | Fundamental software-testing concepts, the role of testing in verification and validation, and principles such as exhaustive testing |
| BS ISO/IEC/IEEE 29119-2:2013 | Test processes | 2013 | Multi-layer test process model, organizational/management/dynamic test processes |
| BS ISO/IEC/IEEE 29119-3:2013 | Test documentation | 2013 | Test document templates and content requirements, full/tailored conformance |
| BS ISO/IEC/IEEE 29119-4:2015 | Test techniques part (scanned edition) | 2015 | Summarized from public domain knowledge; involves test design techniques |
| BS ISO/IEC/IEEE 29119-5:2016 | Keyword-driven testing part (scanned edition) | 2016 | Summarized from public domain knowledge; involves keyword-based test methods |
💡 Part 1 “Software Testing Concepts” explains the role of testing in verification and validation (V&V) and stresses that “exhaustive testing is not feasible”, guiding test resources toward the highest-risk areas.
3. Key Technical Requirements 🔧
3.1 Concepts and Definitions (Part 1)
Part 1 defines the core concepts of software testing, including the role of testing in verification and validation, the division of test levels, and principles such as “exhaustive testing is not feasible”, establishing a unified terminology basis for the whole series.
3.2 Test Processes (Part 2)
Part 2 defines the multi-layer test process model, covering organizational test processes, test management processes, and dynamic test processes. It specifies inputs/outputs and responsibilities for activities such as test planning, test design, test execution, and test recording, making test activities manageable and reproducible.
3.3 Test Documentation (Part 3)
Part 3 specifies the types, structures, and content requirements of test documents, including templates for test strategy, test plan, test cases, and test reports, and defines both full conformance and tailored conformance to balance rigor and flexibility.
✅ Adopting the 29119 series can significantly improve a test team’s process maturity: unified terminology reduces communication cost, standardized processes enhance reproducibility, and standardized documentation facilitates audit and measurement.
4. Engineering Practice and Applications 🛠️
- 🔍 Test management: establish organizational and management test processes per Part 2, clarifying responsibilities and deliverables.
- 🔧 Documentation roll-out: organize test plans, cases, and reports with Part 3 templates to support audit and measurement.
- 📊 Test design: design cases with Part 4 test techniques to improve defect-detection efficiency.
- 📋 Automation and keyword testing: carry out keyword-driven automation per Part 5 to improve regression efficiency.
⚠️ In practice, note that 29119 provides a “tailorable” framework rather than rigid templates; tailor it reasonably according to project scale and risk to avoid document overload leading to process rigidity.
5. Frequently Asked Questions ❓
❓ Q: Why is a unified software testing standard needed?
A: Unified terminology and processes make test activities measurable, comparable, and improvable, reducing communication cost between teams and organizations and improving test quality and efficiency.
A: Unified terminology and processes make test activities measurable, comparable, and improvable, reducing communication cost between teams and organizations and improving test quality and efficiency.
❓ Q: Does 29119 conflict with Agile/DevOps testing practice?
A: No. 29119 defines a tailorable process framework; agile teams can tailor documentation and processes as needed while retaining the standard’s core principles.
A: No. 29119 defines a tailorable process framework; agile teams can tailor documentation and processes as needed while retaining the standard’s core principles.
❓ Q: Are the test document templates mandatory?
A: Part 3 allows both full conformance and tailored conformance; teams can adjust the document scope to project characteristics as long as the tailoring is reasonable.
A: Part 3 allows both full conformance and tailored conformance; teams can adjust the document scope to project characteristics as long as the tailoring is reasonable.
🔍 Q: How much effort is needed to implement 29119?
A: Effort depends on the degree of tailoring — from core process review to full documentation; the key is making processes visible and assessable while avoiding formalism.
A: Effort depends on the degree of tailoring — from core process review to full documentation; the key is making processes visible and assessable while avoiding formalism.