Contents
Introduction
Within Azure Dev Ops, we can also run the Test Cases that have been written. Even when we automate the tests in Test Panel, we may still want to run the Test Cases in Azure Dev Ops, and attached evidence from Test Panel that the test has been successfully completed.
It can also be useful to manually run them for Service Panel Forms, or other UI interfaces where we need to check that the UI looks correct as well as functions correctly.
Where a test is not working as expected, it also gives us the ability to record each step, and give the engineer building the solution as much information as possible, about where the defect occurs.
Azure Dev Ops Browser Add-on
Before we start running the tests, it is recommend to use Edge, and install the Test & Feedback extension. This extension allows us to take screenshots, record short videos, and pickup all user actions while running a test. This allows us to collect the evidence for the change board that we have completed the testing and it is working as expected, or to pickup where the defects are, and give the engineers as much information as possible when attempting to fix the issue. While it does work in other browsers, I have found for the best experience, it is recommend to use Edge.
The extension can be installed from the following URL:
Test & Feedback - Visual Studio Marketplace
Running the tests
The guide below documents how to run a test, and use the Test & Feedback extension to capture a recording of that test.
| Step | Image |
| Log in to Azure Dev Ops, and go to Test Plans | |
| If it does not default to the correct Test Plan, use the back button to view all the test plans, and select the required one | |
| Click the required test plan | |
| Make sure you are on the execute tab (Only Test Admins will see the Define tab), and select the test suite with the test you want to run in. | |
| There could be multiple tests, assigned to multiple users. To see only your tests, you can use the filters. Click the filter button. | |
| The filter toolbar will now appear, and you can select Tester, and set it to Me | |
| Only tests assigned to you are visible. When viewing the test results, all results from all users will be visible | |
| Right click on the test you want to Run, and select Run | |
| Select Run for web application | |
| This will now load the test plan, with the instructions to follow. | |
|
Before you start going through the instructions, if the extension has been installed, you can click the record When the prompt appears, select the screen to share, and click Share |
|
|
The recording will now start |
|
|
You can now run through the steps on the test, ticking each one off as you go. |
|
|
If you need to pause the test, and wait for an action to occur, you can do this by selecting pause from the results button at the top |
|
|
Stop the recording, select the Pause Test, and click save and close. The test will now show as paused. |
|
|
To resume the test, right click on it, and select Resume test, resume for web Application |
|
|
This will allow you to pick up from where you started. If you just click Run, it will start a new test, and the previous one will be marked as a failure. |
|
|
Once all the steps have been completed, you can now set the status to passed, and save the test. |
|
|
On the main screen, it will now show as Passed. |
|
|
To view the history of the test, double click it. |
|
|
You can double click on the test results to view more information. The video recording can be seen as an attachment at the bottom of the screen. |
Creating a defect
Not all tests are going to pass first time, and users are going to need to raise defects. The following guide goes through the process of raising a defect.
| Step | Image |
| Log in to Azure Dev Ops, and go to Test Plans | |
| If it does not default to the correct Test Plan, use the back button to view all the test plans, and select the required one | |
| Click the required test plan | |
| Make sure you are on the execute tab (Only Test Admins will see the Define tab), and select the test suite with the test you want to run in. | |
| There could be multiple tests, assigned to multiple users. To see only your tests, you can use the filters. Click the filter button. | |
| The filter toolbar will now appear, and you can select Tester, and set it to Me | |
| Only tests assigned to you are visible. When viewing the test results, all results from all users will be visible | |
| Right click on the test you want to Run, and select Run | |
| Select Run for web application | |
| This will now load the test plan, with the instructions to follow. | |
|
Before you start going through the instructions, if the extension has been installed, you can click the record When the prompt appears, select the screen to share, and click Share |
|
|
The recording will now start |
|
|
You can now run through the steps on the test, ticking each one off as you go. |
|
|
If a step fails, it will allow you to enter a comment for why it has failed. Enter as much information as possible. It can be useful to include links to the record in Time Traveller. If you have access to a workflow or fixture which did not work, including a link to the history of that item can also be useful. The more information you provide, the easier it will be for the engineer to identify and fix the issue. |
|
|
You can also stop the recording, and take a screenshot |
|
|
The screenshot and comment will be visible . |
|
|
We can now set the status to failed on the top toolbar, and click the save button (Not Save and Close) |
|
|
To create the defect, we click the Create defect |
|
|
This will open the defect creation screen. It will have filled in the Repro steps based on the steps taken when running the test. We need to enter a name for the defect. |
|
|
We can then add additional comments in the discussion field, or tag users that have an interest in the defect. |
|
|
Before we close the defect, we need to link it to the User Story we were testing. Click the Add an existing work item as a parent link |
|
|
If you know the ID of the user story, you can enter it here, otherwise type the name to try and find it. |
|
|
Select the User Story |
|
|
Click Add Link |
|
|
Now click Save and Close on the defect |
|
|
Click Save and Close on the Test Run |
|
|
To view the history of the test, double click it. |
|
|
You can double click on the test results to view more information. We have a clear link to the defect from this screen, and can see the progress of it. |
|
|
If we go to Boards, and select backlog |
|
|
We can see the defect now appears under our User Story. This makes them Defects easier to track and manage. |
|
|
If we click on the Defect, we can view the defect information, and record the time it has taken to fix this defect. If we go to Boards, and Queries, we can create a query to return all defects |
|
|
Click New query |
|
|
Set the Filter to the following Work Item Type = Bug State <> Resolved State <> Closed |
|
|
Run the query to view the results |
|
|
Save the query, and it can now be used during the UAT Review calls to monitor and track the defects being raised. Enter a Name, and Folder and click Ok |
Comments
0 comments
Please sign in to leave a comment.