AZ-400 ยท Flow of work and traceability
Source, bug and quality traceability
Linking work items to commits, PRs, builds, releases and test results; bug-to-fix and requirement-to-test traceability; the Development and Deployment links.
Key points
- A work item can be linked to commits, pull requests and branches (shown in its Development section), to builds (Integrated in build, Found in build), to release deployments (Integrated in release environment) and to test cases and results (Tested by / Tests).
- With these links you can trace a requirement to the tests that verify it, a bug to the commit and build that fixed it, and a release to the work it contains.
Source: https://learn.microsoft.com/en-us/azure/devops/boards/queries/link-type-reference?view=azure-devops
Practice questions
Which Azure Boards link type connects a test case to the user story it validates?
- Duplicate Of
- Tested by / Tests
- Predecessor / Successor
- Related
Show answer
Answer: B. Tested by / Tests
Tested by (from the story) and Tests (from the test case) form that pair. Related is a generic non-directional link and Duplicate Of is for duplicates.
Which GitHub objects can be linked to an Azure Boards work item when the repository is connected?
- A commit
- A GitHub Packages feed
- An issue
- A pull request
- A Microsoft Teams channel
Show answer
Answer: A. A commit, C. An issue, D. A pull request
GitHub commits, issues and pull requests are GitHub link types. A package feed and a Teams channel are not linkable GitHub objects.
If you delete the AB# text from a pull request description, the link stays visible in the PR's Development section.
Show answer
Answer: False
False. Those links are driven by the AB# text in the description; removing it removes them.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
