For QA leads and teams that hand test evidence to customers or auditors

Test reports from Azure DevOps Test Plans

Give customers or reviewers a test report they can read outside Azure DevOps. Bravo Notes brings test steps, expected results and suite outcome counts into a saved template. Add linked requirements when you need traceability, then export PDF, HTML or Markdown. Test Plans integration requires the Bravo Notes Business plan or above.

Start free trialSee the template and example ↓

30 days, every feature, no credit card. The trial does not convert into a paid plan automatically.

Steps, outcomes and coverage in one document

A test report needs more context than a list of test cases. Reviewers may need the steps, expected results, execution summary and links to requirements together. Choose those sections in a Bravo Notes template and reuse it for the next test cycle.

What goes into the document

  • Selected test cases with their steps and expected results in a table. Extend the template to include step attachments.
  • Passed, failed, blocked and not run counts for a test plan and suite, optionally for one configuration.
  • An optional traceability section listing linked test cases and flagging selected requirements without a test link.
  • Product, version and date from parameters, plus a PDF cover page and page numbers for the document control block.

Illustrative report · Fictional data

Orderflow 4.12 test report

Suite 118: Checkout

Passed
8
Failed
1
Blocked
0
Not run
1

Test case 204: Apply a discount code

StepExpected result
Open the checkout.The order summary is displayed.
Enter a valid discount code.The order total includes the discount.

Linked requirements

RequirementTest case
REQ-92: Apply checkout discounts204: Apply a discount code
Illustrative test report with fictional data: suite outcome counts, test steps and expected results, and linked requirements. Not a captured Bravo Notes export; the traceability section requires extending the starter template.

Build the document in Azure DevOps

  1. Step 1

    Load the test cases

    Add them with a saved query, for example all test cases under an area path or with a tag. Test cases are work items, so everything the query returns is available to the template.

  2. Step 2

    Add outcomes and coverage

    Set the plan and suite IDs in the starter to add outcome counts. If you also need traceability, extend the template with a section that follows Tested By links from your selected requirements.

  3. Step 3

    Check one case, then export

    Compare the preview with the selected plan, suite and test cases in Azure DevOps. Export PDF, HTML or Markdown. To regenerate the report after a test run, add the Bravo Notes task to the pipeline that runs your tests.

Next time

Update the version and, if needed, the plan and suite IDs. Refresh the selected test cases and check the outcome counts before exporting the next report.

Starter template

This starter combines suite outcome counts with steps and expected results for the test cases you load. Replace the plan and suite IDs with your own, and check that the query, suite and configurations cover the intended scope. The query and suite are separate inputs; suite counts can include multiple test points for one case. Step attachments, per-case outcomes and requirement links need additional template sections. Test Plans integration requires the Bravo Notes Business plan or above.

Paste into the Template tab

# Test report: {{ param 'ProductName' }} {{ param 'Version' }}

Prepared {{ date format='d mmmm yyyy' }}

## Summary

{{#testCaseSummary testPlanId=112 testSuiteId=118}}
| Total | Passed | Failed | Blocked | Not run |
|-------|--------|--------|---------|---------|
| {{ totalTests }} | {{ passedTests }} | {{ failedTests }} | {{ blockedTests }} | {{ notExecutedTests }} |
{{/testCaseSummary}}

## Test cases

{{#workItems orderBy='Id'}}
### {{ id }}: {{ field 'Title' }}

<table>
<thead>
<tr><th>#</th><th>Step</th><th>Expected result</th></tr>
</thead>
<tbody>
{{#testSteps}}
<tr><td>{{ no }}</td><td>{{{ step }}}</td><td>{{{ expectedResult }}}</td></tr>
{{/testSteps}}
</tbody>
</table>

{{/workItems}}

Parameters to fill in on the Parameters tab: ProductName, Version

Start with fields, sections and linked items in the syntax reference.

Example document excerpt

Test report: Orderflow 4.12

Prepared 11 November 2026

Summary

TotalPassedFailedBlockedNot run
2422101

Test cases

2041: Sign in with a valid account

#StepExpected result
1Open the sign-in pageEmail and password fields are shown
2Enter valid credentials and submitThe dashboard opens and shows the user name

Illustrative excerpt with fictional work items. This is not a captured Bravo Notes export; your template, data and export settings determine the final document.

We currently build your first custom template for free during your trial.

Contact us

“We use Bravo Notes for release notes and test reports from DevOps test plans. In both cases it helps us to link the information from DevOps in a neat way to the application (release Notes) or a test report for the customer.”

Laurens Noorland, Team Lead IT at DWG. Read customer reviews on the Visual Studio Marketplace.

What you need

  • Bravo Notes Business or Enterprise subscription plan for the Test Plans integration: test steps, step attachments, suite summaries and per-case results.
  • Read access to the test plan and its runs for the user or pipeline identity that generates the report.
  • The plan and suite IDs from the Test Plans URL for the summary table.

Plans apply to one Azure DevOps organization and include named seats for document creators. Readers of exported files do not need a Bravo Notes license. Links back to work items still require Azure DevOps access. Compare plans.

Frequently asked questions

Can the report include the screenshots testers attached to steps?
Yes. Extend the testSteps block to include step attachments; the starter above shows only steps and expected results. Images in work item fields can also be embedded in the PDF.
Does it show pass and fail per test case, not only per suite?
Yes. The testCaseSummary helper gives the counts per plan and suite. The testCaseResult and step result helpers give the outcome per test case and per step; ask support for the sample template that combines them with the step table.
How do I show which requirements have no tests?
Load the user stories and follow the Tested By link in a linkSection block. Its else branch prints a warning for every requirement without a linked test case, so gaps show up instead of disappearing.
Can the report be generated after every test run?
Yes. Add the Bravo Notes build task to the pipeline that runs your tests, with the query as its work item source. It renders the saved template and can publish the output to a file, Wiki, repository or Confluence. The suite summary is not automatically limited to that pipeline run; check the selected plan, suite and configuration scope.

Go deeper

Try test reports with your own work items

Install Bravo Notes in your Azure DevOps organization. Start with a small selection of work items, adapt the template above and check the preview before exporting your first document.

Start free trial

30 days, every feature, no credit card. The trial does not convert into a paid plan automatically.

Compare plans