Introduction

Within Azure Dev Ops, it is possible to run and capture testing evidence. In this article, we will look at how this data can be exported and shared with users who need to view it, such as the key stakeholders who will approve the go-live, or the change review board who will sign off the deployment.

Instructions

The following guide goes through the process of producing a report which shows the test results. It also includes the steps of the test which are being run, and also a link to the User Stories, and any potential defects which have been created.

It can be emailed directly to users, or exported as a PDF and then shared with the required users, or attached to any upcoming changes.

To produce this report, you will need to have a Test Plan license in Azure Dev Ops.

Steps	Images
Log in to Azure Dev Ops, and go to Test Plans
Right Click on the top test suite
Select Export
There are several options to choose from.  We do not need all the information, so some checkboxes can be removed, but it is worth trying a few different options out and find what works best for you.
The difference between Email and Print is minimal. If you select Print, you can print it out, or you can save it to a PDF. As you can see, the links in the document are clickable, and allow the users with access to do directly to Azure Dev Ops and view the information
The Email format is identical, although the styling might be a little more appealing.
With the email approach, you can select who it is being sent to, and add a note for the users it is being sent to, to view
With all the links being clickable, especially the latest Test Outcomes, it can be worth granting key stakeholders and the change board team access to Azure Dev Ops as Stakeholders (They do not require a license). This will allow those users to click on the links, and view the evidence of the testing which has taken place.