Enable Traceability Between Requirements, Test Cases, and Bugs in Azure DevOps

Different work item types in Azure DevOps (such as Requirements, Test Cases, and Bugs) – and even development artifacts such as code check-ins etc. – should be linked together to provide supporting information when needed. Though you can always add links manually, there are certain setups that will help facilitate this more efficiently. The setup below is one of the most typical configurations and can be very helpful.

Note: This setup assumes that the team has Requirements/User Stories/PBIs written. If the team doesn’t have them, you can still create a Static Test Suite (in Step 2) and Run the Test and creating a bug from there with some supporting information (in step 3).

1. When writing a Test Case, have it link to the Requirement/User Story/PBI work item with the “Tests” link/relationship type.

2. Create a Requirement-based Test Suite for the Requirement/User Story/PBI work item. This will also enable the Suite to automatically include any additional test cases that “test” that Work Item in the future.

3. Run the Test using the Run button from the Requirement-based Suite. If a step fails, click “Create a bug” from the Test Runner, and all relevant information will be filled in for the Bug, including:
• Repro steps (based on the Test Case’s steps).
• Parent Work Item (of that same Test Case).
• Related Test Case (the one being run).

Create a bug from Test Runner

Facebook