Enhanced Export PROExport complete test execution evidence
Introduction
Enhanced Export PRO enables you to generate comprehensive test execution evidence directly from your Test Plans. Instead of exporting only test definitions or summary results, you can create a complete execution document that includes all testing activities, execution outcomes, tester comments, attachments, screenshots, and supporting evidence.
This capability is particularly valuable for audits, compliance reporting, customer acceptance testing, and release sign-off documentation.
Data integrity
Each export is a point-in-time snapshot of your Test Plan. Azure DevOps identifiers, execution timestamps, and tester attribution are preserved on every record, so auditors and reviewers can always trace an entry in the exported document back to its source in Azure DevOps. In most cases, they are even directly linked.
Scope
All test plan exports are done in the scope of a test plan and can provide traceability between planned and executed test effort, test case to requirement traceability, and evidence of what has been tested. If you’re looking for requirement-centric evidence or traceability, those needs can be met by Work Item Query exports. For example:
-
Requirement Specification Export deep details about the requirements, the test cases and outcome from potential multiple test plans.
-
Traceability Report Exports a traceability grid suitable for Requirement to Test case traceability, with outcome from potential multiple test plans.
What Is Included in the Export?
Enhanced Export PRO can generate a detailed evidence package containing:
- Test Plan information & Structure
- Test execution summary
- Individual test cases
- Test result at the test point level: test case, configuration, tester, and outcome (Passed, Failed, Blocked, etc.)
- Test step level result (action, expected result, actual result)
- Execution dates and tester information
- Comments and notes
- Filed Defects (linked to execution)
- Attachments
- Embedded screenshots
The resulting document provides a complete record of what was planned to be tested, how and then the individual test was executed, and the evidence collected during testing. Enhanced Export PRO preserves Azure DevOps identifiers, execution timestamps, tester attribution, result status, linked defects, comments, and attachments, allowing auditors and stakeholders to trace exported information back to the original Azure DevOps records.
Common Use Cases
| Use Case | Description |
|---|---|
| Audit Evidence | Generate a complete testing evidence package for internal or external audits, including execution history, screenshots, and supporting documentation. |
| Regulatory Compliance | Provide documented proof that required test procedures were executed and validated. |
| User Acceptance Testing (UAT) | Deliver a detailed execution report showing test outcomes and supporting evidence for customer review and approval. |
| Release Sign-Off | Create a comprehensive testing record that demonstrates readiness for production deployment. |
Exporting Test Execution Evidence
- Navigate to the Test Plan that you want to export documentation for
- Select the Export tab
- Select the template Test Execution Log
This will produce an export like:
Configure what to include in the report
Click the Options button to configure what you want to include in the export.
Options
Below is a short description of the different options you can check and what it will bring.
Include Test results details
Checking the Include Test Results details will show results on the test step level, including attachments & comments.
Generate a document for archiving, storage, or sharing
Click Open and select your desired word template you want to use for formatting.
Enhanced Export PRO will generate a Word document and embed images and other attachments in the document.
Retention and Storage
Once generated, the exported Word document is a static file with no further connection to Azure DevOps. We recommend the following practices for audit and compliance use:
- Name files consistently, including the Test Plan name and export date, for example TestPlan-1234_ExecutionEvidence_2026-06-17.docx.
- Store exports in a controlled location, such as a document management system or a dedicated, access-controlled folder, rather than ad hoc local copies.
- Re-export before any audit or sign-off deadline if the Test Plan has changed since the last export, so the evidence reflects the current execution state.
- Treat each export as a dated snapshot. If your process requires version history or formal document control, manage that at the storage layer; Enhanced Export PRO does not version exported documents.