AZ-400 Question 28
Select 3Your team is building a .NET application using Azure DevOps. They want to capture test pass/fail rates, code coverage data, and track these metrics over time. They also plan to create custom dashboards and analytics queries in Azure DevOps for deeper insights into test reliability. You are configuring their CI pipelines to support these goals. Which three actions should you recommend to ensure that test metrics and coverage data are accurately collected and displayed in Azure DevOps?
- A
Add a 'Publish Test Results' task in each pipeline to store build and test outcomes in Azure DevOps.
- B
Write a script that copies raw coverage files to an external Blob Storage account for later analysis.
- C
Use the 'Publish Code Coverage Results' task in the pipeline to generate and report coverage metrics.
- D
Use the Analytics extension or built-in Analytics views in Azure DevOps to create custom dashboards for test metrics.
- E
Rely solely on build logs for capturing coverage details, which automatically populates advanced analytics.
Show answer and explanation
Correct answers: A, C, D
Explanation
By publishing both test results and code coverage metrics via dedicated pipeline tasks (Options 1 and 3), you ensure Azure DevOps has the data it needs for analysis. Leveraging the Analytics extension or built-in Analytics views (Option 4) then provides flexible dashboards and queries where you can gain insights into trending pass rates, coverage levels, and other key performance indicators. Microsoft� documentation offers detailed guidance on using the Publish Test Results and Publish Code Coverage Results tasks, as well as setting up custom Analytics dashboards for metrics-based reporting.
- A. Correct.
Correct. The 'Publish Test Results' task processes your test run data and uploads pass/fail information to Azure DevOps, enabling the platform to store and display these results in test summary views and analytics.
- B. Incorrect.
Incorrect. Simply copying coverage files to an external storage location does not automatically make them available for querying or analytics in Azure DevOps. Additional integrations or tasks would be required.
- C. Correct.
Correct. Including the 'Publish Code Coverage Results' task will generate a coverage report that Azure DevOps can interpret and display in your build summary. This also feeds data into Azure DevOps analytics for historical tracking.
- D. Correct.
Correct. The Analytics extension or built-in Analytics views allow you to build custom dashboards and queries, giving you insights into test pass rates, coverage trends, and other metrics over time.
- E. Incorrect.
Incorrect. While build logs provide a basic summary of test results, they do not automatically capture detailed coverage data or enable historical queries. Relying solely on logs misses the benefits of Azure DevOps test analytics features.