Woodgrove Bank must prove to a regulator that every user story released in a quarter was covered by at least one passing test, and must show the evidence per story rather than per test run. The team uses Azure Boards, Azure Test Plans, and automated tests published from a YAML pipeline. What should you implement?
- A.
Create requirement-based test suites that link test cases to the user stories, and add the Requirements quality widget to the team dashboard.
- B.
Tag every automated test with the identifier of the story it covers, export the test run summary to a CSV file after each release, and keep the files in a compliance folder for the auditor.
- C.
Enable code coverage publishing in the pipeline and set a build validation policy with a minimum coverage threshold.
- D.
Add the Test results trend (Advanced) widget to the dashboard and filter it by the release pipeline.
Show answer
Answer: A
Requirement-based test suites bind test cases to work items, and the Requirements quality widget reports pass or fail evidence for each linked requirement.
- A. Requirement-based suites create Tested By links from test cases to stories, and the Requirements quality widget reports outcomes per story.
- B. Tag-and-export is manual bookkeeping outside the work item graph; it creates no durable link and is not reproducible for an audit.
- C. Code coverage proves which code executed, not which requirement was verified, and a threshold policy produces no requirement-level evidence.
- D. The trend widget aggregates results per pipeline over time and offers no pivot by user story, so it cannot show per-requirement evidence.