IEEE 29119-2-2013

29119-2-2013 is a software and systems engineering standard focused on software testing test processes, giving a structured way to plan and manage testing activities. In the computing and processing field, it helps define how test work should be organized so results are more consistent, traceable, and useful for decision-making. As part of the 29119 series, it is relevant where testing needs clear process control and repeatable practice.

29119-2-2013 overview

This standard addresses the test process portion of software testing, describing how testing activities can be structured within software and systems engineering work. The subtitle shows that its emphasis is on test processes rather than a single test technique or tool, making it useful for organizations that need a common approach to planning, execution, and reporting. 29119-2-2013 is especially relevant where test work must support quality management, project control, and dependable software delivery in computing environments.

Typical use cases

29119-2-2013 is commonly used when defining test workflows for software products, system integration work, or verification activities within computing projects. It may support teams building business applications, embedded software, or other systems where testing needs to be repeatable and aligned across roles. The standard can also be useful during procurement or contract work when test process expectations must be stated clearly, or when organizations want a shared framework for test planning, execution, and review.

Why this standard matters

Clear test process guidance helps reduce ambiguity in how testing is organized and assessed. For teams working to controlled requirements, 29119-2-2013 can improve consistency between projects, support better documentation, and make it easier to compare test outcomes. It also helps reduce risk by encouraging disciplined test management and more reliable evidence for acceptance or release decisions. For organizations in computing and processing, that structure can be important for quality control and auditability.

• Software testing process structure
• Planning, execution, and reporting
• Traceable test management practices
• Support for quality and acceptance decisions
• Useful for computing and systems projects