ISO/IEC/IEEE 29119 is an international series of standards for software testing. It defines vocabulary, test processes, documentation and test design techniques. It is a voluntary standard, not a law and not a certification scheme, so "compliance" here means conformance you claim and can show evidence for. The original title for this topic framed it as an enterprise compliance program; this article covers what the standard is and how to use it.
What it is
The full title is Software and systems engineering — Software testing. It is published jointly by ISO, the IEC and the IEEE, and was developed within the joint ISO/IEC committee for software and systems engineering. It was designed to consolidate and replace older testing standards, including IEEE 829 (test documentation), IEEE 1008 (unit testing) and the British Standard BS 7925.
It is a multi-part series. The parts most teams meet are:
- Part 1: General concepts – vocabulary and core ideas such as risk-based testing and the test levels and types.
- Part 2: Test processes – a layered process model.
- Part 3: Test documentation – templates and content for test work products.
- Part 4: Test techniques – specification-based, structure-based and experience-based techniques.
- Part 5: Keyword-driven testing – a framework for keyword-based automation.
- Part 11: Testing of AI-based systems – guidance published as a technical report, not a requirements standard.
Parts 1 to 4 were revised in the early 2020s. The series has changed over time, so check the current edition of each part you cite.
The standard has been controversial. Parts of the testing community, especially the context-driven school, have criticized it as too prescriptive and not grounded in empirical evidence. The standard allows tailoring, and a sensible adoption treats it as a reference model, not a rulebook.
Who it applies to
To the best of current knowledge, no jurisdiction requires ISO/IEC/IEEE 29119 by law. It is relevant to any organization that builds or buys software and wants a defined, repeatable testing practice. Common drivers include:
- Contracts, especially in government, defense, finance and other large-enterprise procurement, that ask for testing to follow a recognized standard.
- Regulated product domains (automotive, medical devices, aviation, rail) where domain standards require documented verification. 29119 is not a substitute for those standards, but it can supply process and documentation structure alongside them.
- Large or outsourced testing organizations that need a common vocabulary and work-product set across teams and suppliers.
Small teams practicing agile or exploratory testing can use parts of it, such as the test techniques in Part 4, without adopting the full documentation set.
Key requirements and control areas
Layered test process model (Part 2)
Part 2 organizes testing into three layers:
- Organizational test process – developing and maintaining the organizational test policy and organizational test practices (called the organizational test strategy in the 2013 edition).
- Test management processes – test planning, monitoring and control, and test completion.
- Dynamic test processes – test design and implementation, environment set-up and maintenance, test execution, and incident reporting.
Test documentation (Part 3)
Part 3 describes the content of work products. They include the organizational test policy and strategy, test plan, test status and completion reports, test design and test case specifications, test procedures, test data and environment requirements and readiness reports, actual results, and incident reports. The standard expects you to tailor the set to project size and risk. You do not have to produce every document as a separate artifact if the information is captured elsewhere.
Risk-based testing
Testing effort is prioritized by risk analysis, so test planning links product and project risks to test depth and scope.
Test design techniques (Part 4)
- Specification-based – equivalence partitioning, boundary value analysis, state transition testing, combinatorial approaches and similar.
- Structure-based – statement, branch and decision coverage, and stronger coverage measures.
- Experience-based – such as error guessing.
Traceability and measurement
Tests should trace to test conditions and requirements, and monitoring should produce measures that support decisions about when testing is complete.
Assessment, audit and enforcement
No regulator enforces the standard and no body issues an organizational "ISO 29119 certificate" under ISO itself. ISO does not certify conformity to its standards; that is done by independent certification bodies, and no established accredited certification scheme for 29119 comparable to ISO 27001 certification is known. Conformance is claimed in these ways:
- Self-declaration – Part 2 supports claiming full conformance or tailored conformance, where you state which outcomes you tailored out and why.
- Customer or internal audit – a client or your quality function checks your test artifacts against the standard or a contractual subset.
- Third-party assessment – consultancies offer process assessments, but these are not the same as accredited certification.
Because there are no statutory penalties, the consequences of non-conformance are contractual or commercial. Individual training certificates exist from third parties, but they certify a person's knowledge, not an organization's conformance.
A practical path to adopting it
- Decide the purpose. Is it a contractual requirement, an internal quality baseline, or a supplier-alignment tool? This sets how formal your conformance claim must be.
- Obtain the current editions of the parts you will cite and note their year and edition in your policy.
- Baseline current practice. Compare your testing against the Part 2 processes and Part 3 work products and record gaps.
- Define a tailoring statement. Say which processes and documents apply to which project types (for example, safety-relevant versus internal tools) and justify omissions.
- Write the test policy and strategy. These sit at the organizational layer and should set risk-based testing rules, test levels, entry and exit criteria, and tooling.
- Adapt templates. Map Part 3 content to artifacts you already produce in your test management, issue tracking and CI systems rather than creating parallel documents.
- Adopt Part 4 techniques in test design guidelines, with coverage expectations by risk level.
- Collect evidence from normal work. Test plans, execution results, defect records and completion reports should come from the tools teams already use, with traceability to requirements.
- Review and improve. Use test completion reports and retrospectives to update the strategy, and re-check when the standard is revised.
How it maps to other frameworks
These are overlaps, not equivalences. 29119 covers testing process and documentation in depth; the frameworks below cover wider scope.
- ISO/IEC 27001: Annex A in the 2022 edition includes controls on secure development and on security testing in development and acceptance. 29119 can provide the process structure, but it does not address security testing specifically or the management system as a whole.
- SOC 2: change management and system operations criteria expect testing before changes are released. 29119 work products can serve as evidence, but SOC 2 does not require this standard.
- NIST SSDF (SP 800-218): includes practices on testing executable code and verifying software. Part 4 techniques and test records can support those practices, though the SSDF has security-specific expectations that 29119 does not set out.
- ISO/IEC/IEEE 12207 and 15288: these lifecycle process standards sit in the same engineering family and 29119 is intended to be consistent with them.
- Domain safety standards (such as ISO 26262 or IEC 62304): they set their own verification requirements. 29119 may help structure the work but does not satisfy them alone.
FAQs
Is ISO 29119 mandatory?
Not by law. It becomes mandatory only if a contract, customer or internal policy requires it.
Can we get certified to ISO 29119?
There is no ISO-run certification of organizations. You can declare full or tailored conformance and have it reviewed by a customer or independent assessor, but that is not the same as an accredited certificate like ISO 27001.
Does it work with agile and DevOps?
It can, if you tailor it. Much of the documentation can live in test management tools, pipelines and tickets, and lightweight plans can replace formal documents. Heavy up-front documentation is the main friction point.
Does it cover security testing?
Not as a dedicated discipline. Its techniques and processes apply to security test cases, but you would pair it with security-specific guidance such as threat modeling, secure development frameworks and penetration testing practices.
Does it cover testing AI systems?
Part 11 provides guidelines on testing AI-based systems as a technical report. It is informative guidance and does not satisfy regulatory requirements such as those for high-risk AI under the EU AI Act.
How Aristiun helps
Aristiun is the AI-powered compliance automation and threat modeling platform, powered by Ayurak AI. Teams adopting a testing standard still need to prove that testing happens and that it ties to control requirements. Aristiun collects evidence automatically from connected systems such as AWS, Azure, GCP and GitHub, so you do not rely on manual screenshots or spreadsheets, and maps it to the controls that matter across compliance frameworks.
- Map controls across 340+ frameworks with continuous evidence collection, so one evidence base supports testing-related controls in ISO 27001, SOC 2 and others.
- Monitor control effectiveness and get alerts when controls drift out of compliance.
- Use AI-powered gap analysis to check that evidence meets auditor expectations.
- Generate threat models from code, IaC and architecture diagrams to inform risk-based test priorities.