ISO/IEC/IEEE 29119 Test Completion Report: Sections & Template
An ISO/IEC/IEEE 29119 Test Completion Report is a standardized document that wraps up a testing activity: it records what was tested, how results measured up against the exit criteria, what deviated from the plan, which risks remain, and what the team learned. It's the deliverable QA hands to stakeholders to support a release decision — the modern successor to the IEEE 829 Test Summary Report.
What is ISO/IEC/IEEE 29119?
ISO/IEC/IEEE 29119 is the international standard for software testing. It replaced much of the older IEEE 829 standard and is split into several parts:
- 29119-1 — concepts and definitions
- 29119-2 — test processes
- 29119-3 — test documentation (where the Test Completion Report lives)
- 29119-4 — test techniques
- 29119-5 — keyword-driven testing
Sections of a 29119 Test Completion Report
Part 3 (29119-3) describes the content a Test Completion Report should cover. Use this as your template:
| Section | What it covers |
|---|---|
| Overview / Identifier | Unique ID, scope of the report, and references to the test plan and items under test. |
| Testing performed | A summary of what was tested, in which environment, and over what period. |
| Deviations | How actual testing differed from the plan (scope, schedule, environment, or procedure changes). |
| Test completeness | Coverage achieved against the planned scope and the exit criteria — pass/fail counts and open defects. |
| Residual risks | Known risks that remain at release (untested areas, deferred defects, environmental gaps). |
| Reusable test assets | Test cases, data, scripts, and environments worth keeping for future cycles. |
| Lessons learned & recommendations | What to improve next time, plus an overall assessment of release readiness. |
IEEE 829 vs ISO/IEC/IEEE 29119
| Aspect | IEEE 829 (Test Summary Report) | 29119-3 (Test Completion Report) |
|---|---|---|
| Status | Older, superseded | Current international standard |
| Focus | Results summary + evaluation | Process-oriented completion of testing |
| Adds | — | Residual risks, reusable assets, lessons learned |
How to write one, step by step
- Pull the results. Gather pass/fail counts, defect status, and coverage from your test-management tool.
- Compare against exit criteria. State clearly whether the criteria were met.
- Record deviations. Note anything that changed versus the plan.
- List residual risks. Be explicit about what remains untested or deferred.
- Capture reusable assets and lessons. This is what sets 29119 apart from a plain summary.
- Give a release recommendation and capture sign-off.
Generate 29119 reports automatically with BluQueue
Compiling these by hand is slow. BluQueue tracks your test plans, scenarios, cases, and bugs — then generates a complete ISO/IEC/IEEE 29119 Test Completion Report (and the classic IEEE 829 Test Summary Report) from that data with AI, exportable to PDF or Word. Test management, project management, and monitoring live in one tool — see how it stacks up in our BluQueue vs TestRail comparison.
Start free — 30-day Pro Plus trial, no credit card required.
Frequently asked questions
What is an ISO/IEC/IEEE 29119 Test Completion Report?
It is the standardized document defined in ISO/IEC/IEEE 29119-3 that summarizes a testing activity once it is complete — what was tested, the results against exit criteria, deviations, residual risks, reusable test assets, and lessons learned.
What is the difference between IEEE 829 and IEEE 29119?
IEEE 829 is the older test documentation standard; its Test Summary Report was superseded by ISO/IEC/IEEE 29119-3, whose equivalent is the Test Completion Report. The 29119 version is more process-oriented and adds residual risks, reusable test assets, and lessons learned.
Is IEEE 29119 mandatory?
No. It is a widely referenced international standard, not a legal requirement. Teams adopt it (or parts of it) for consistent, auditable test documentation, especially in regulated or enterprise contexts.
Try BluQueue free
Replace your tracker, QA tool, and time tracker with one — no credit card required.
Keep reading
IEEE 829 Test Summary Report: Template & How-To Guide
IEEE 829 Test Summary Report: Template & How-To Guide
What an IEEE 829 Test Summary Report is, the exact sections it must contain, and a step-by-step template you can copy for your next test cycle.
Best Jira Alternatives in 2026 (Free & Paid, Compared)
Best Jira Alternatives in 2026 (Free & Paid, Compared)
The best Jira alternatives in 2026, compared honestly — from all-in-one tools like BluQueue and ClickUp to simpler options like Asana, Trello and Linear.
How to Write a Test Plan (with a Free Template)
How to Write a Test Plan (with a Free Template)
A step-by-step guide to writing a software test plan — the exact sections to include, a copy-ready template, and how a test plan differs from a test case and test strategy.
BluQueue vs Jira
An honest BluQueue vs Jira comparison — pricing, project management, built-in QA and team monitoring, and which tool fits agencies vs enterprise agile teams.