AZ-400 Question 30
Select 2You are a DevOps engineer implementing a new automated testing strategy in Azure DevOps. Your goal is to track pass/fail rates across runs, monitor code coverage trends, and investigate test failures in detail. Which two approaches should you implement to gather and visualize these metrics effectively?
- A
Use Azure DevOps Analytics views to track and graph test pass/fail rates over time
- B
Enable automated test feedback by storing test results in a local CSV file on build agents
- C
Collect code coverage metrics with the Visual Studio Test task and use built-in coverage reports
- D
Manually compile test data into a shared spreadsheet to document coverage and pass/fail ratios
Show answer and explanation
Correct answers: A, C
Explanation
Leveraging Azure DevOps Analytics to create dashboards (Option 1) and gathering code coverage metrics using the Visual Studio Test task (Option 3) are recognized best practices. These approaches enable easy tracking of test pass/fail rates, coverage trends, and detailed failure insights in an automated and scalable manner. Refer to Azure DevOps documentation on Test Analytics (https://learn.microsoft.com/azure/devops/report/analytics/) and code coverage workflows (https://learn.microsoft.com/azure/devops/pipelines/test/codecoverage-for-devops) for more details.
- A. Correct.
Option 1: CORRECT. Azure DevOps Analytics offers built-in views and dashboards that allow you to visualize pass/fail trends, spot regressions, and filter by test suites. This helps teams quickly identify issues and see overall test health.
- B. Incorrect.
Option 2: INCORRECT. Simply storing test results in a local CSV file on build agents does not provide ongoing visibility or easy aggregation of data. You would lose the centralized reporting and trending capabilities that Azure DevOps Analytics provides.
- C. Correct.
Option 3: CORRECT. The Visual Studio Test task in Azure DevOps can produce code coverage data, which can then be visualized using the built-in coverage reports. This allows the team to analyze coverage changes over time and focus on untested areas.
- D. Incorrect.
Option 4: INCORRECT. Manually compiling test data into a spreadsheet is error-prone and not sustainable. It lacks automated data refresh, easy trend visualization, and collaboration features available through Azure DevOps native tools.