Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC TR 29119-13 — Software Testing Terminology
A Comprehensive Reference for Standardized Software Testing Vocabulary
Introduction to ISO/IEC TR 29119-13
The ISO/IEC 29119 series of standards provides a globally recognized framework for software testing processes, documentation, techniques, and tools. Within this series, ISO/IEC TR 29119-13 serves as the foundational terminology reference that harmonizes the vocabulary used across all software testing activities. As a Technical Report, it consolidates definitions from multiple sources including ISO/IEC 24765 (Systems and Software Engineering Vocabulary), ISTQB (International Software Testing Qualifications Board) glossary, and IEEE standards, creating a unified lexicon for the software testing profession.
The importance of standardized terminology in software testing cannot be overstated. When team members across different organizations, countries, and domains use the same terms with the same meanings, communication becomes more precise, testing artifacts become more consistent, and the risk of misinterpretation is dramatically reduced. This is especially critical in safety-critical domains such as automotive (ISO 26262), aerospace (DO-178C), and medical devices (IEC 62304), where testing terminology directly impacts regulatory compliance and safety assessments.
When adopting ISO/IEC 29119-13 terminology in your organization, create a glossary mapping your existing terms to the standard definitions. This eases the transition and helps teams align with international practices without disrupting ongoing projects.
Core Terminology Categories
ISO/IEC TR 29119-13 organizes software testing terminology into several key categories that span the entire testing lifecycle. Understanding these categories is essential for effective test planning, execution, and reporting.
Test Artifact Terms
The standard defines fundamental artifact-related terms that form the backbone of testing documentation. A test case is a set of preconditions, inputs, actions, expected results, and postconditions developed to verify specific requirements. A test procedure specifies the sequence of actions for executing a set of test cases, while a test suite groups related test cases or procedures for a specific test level or objective. The test scenario describes a sequence of test cases or procedures that together validate a user story or business process. These distinctions are critical: a test case answers “what to test,” a test procedure answers “how to execute,” and a test scenario answers “what real-world situation is being validated.”
Test Level and Type Terms
The terminology around test levels and types is particularly important for structuring testing efforts. Test level refers to a group of testing activities organized and managed together, such as component testing, integration testing, system testing, and acceptance testing. Test type describes the characteristic of the test objective, such as functional testing, performance testing, usability testing, and security testing. The standard makes a clear distinction: test levels address the scope of testing (what is being tested), while test types address the quality characteristics being evaluated. This separation allows test managers to design comprehensive test strategies that ensure both breadth and depth of coverage.
A common pitfall in test documentation is confusing test conditions with test cases. A test condition describes an aspect of the test item verifiable by a test, while a test case includes specific input values and expected results. Always ensure your test cases have concrete, measurable expected results.
Engineering Insights for Terminology Adoption
Implementing standardized terminology from ISO/IEC TR 29119-13 in real-world engineering environments requires thoughtful planning. One effective approach is to perform a terminology gap analysis, comparing your organization’s current vocabulary against the standard definitions. This analysis should involve representatives from development, quality assurance, product management, and customer support to ensure all perspectives are captured.
| Current Term (Legacy) | Standard Term (ISO/IEC 29119-13) | Impact of Change |
|---|---|---|
| Test Script | Test Procedure | Clarifies that it defines execution sequence, not automation code |
| Test Scenario | Test Condition or Test Scenario (context-dependent) | Reduces ambiguity in test planning documents |
| Bug / Defect | Fault → Failure (distinction) | Improves root cause analysis accuracy |
| Unit Test | Component Testing | Aligns with international standards terminology |
| Regression Testing | Regression Test (specific type) | Helps distinguish from retesting |
Beyond mere adoption, engineering teams should consider integrating the standardized terminology into their test management tools and CI/CD pipelines. This can be achieved by configuring test management systems (such as Jira/Xray, Azure Test Plans, or HP ALM) to use the standard classification fields. Furthermore, automated test reporting tools should be updated to reflect the correct terminology, ensuring that dashboards and compliance reports speak the same language as the international standards community.
Organizations that adopted ISO/IEC 29119-13 terminology report a 30-40% reduction in test documentation review cycles, as reviewers spend less time clarifying ambiguous terms and more time evaluating technical content.
FAQs
Q: What is the difference between a test case and a test procedure?
A test case defines the inputs, preconditions, expected results, and postconditions for a specific objective. A test procedure specifies the step-by-step execution sequence for running one or more test cases. In practice, a test case is the ‘what’ and a test procedure is the ‘how.’
A test case defines the inputs, preconditions, expected results, and postconditions for a specific objective. A test procedure specifies the step-by-step execution sequence for running one or more test cases. In practice, a test case is the ‘what’ and a test procedure is the ‘how.’
Q: How does ISO/IEC TR 29119-13 relate to ISTQB terminology?
ISO/IEC TR 29119-13 harmonizes definitions from ISTQB, IEEE, and ISO/IEC 24765. While ISTQB focuses on certification and best practices, the ISO technical report provides a broader, internationally agreed vocabulary. Both are largely aligned, but the ISO document covers a wider scope including terms from systems engineering and safety-critical domains.
ISO/IEC TR 29119-13 harmonizes definitions from ISTQB, IEEE, and ISO/IEC 24765. While ISTQB focuses on certification and best practices, the ISO technical report provides a broader, internationally agreed vocabulary. Both are largely aligned, but the ISO document covers a wider scope including terms from systems engineering and safety-critical domains.
Q: Should my organization adopt the terminology if we are not required to comply with ISO 29119?
Yes. Standardized terminology improves communication efficiency, reduces onboarding time for new team members, and simplifies collaboration with external partners and contractors. Even without formal compliance requirements, the terminology investment pays dividends through reduced ambiguity and improved test artifact quality.
Yes. Standardized terminology improves communication efficiency, reduces onboarding time for new team members, and simplifies collaboration with external partners and contractors. Even without formal compliance requirements, the terminology investment pays dividends through reduced ambiguity and improved test artifact quality.
