Code Coverage Excel Report

TFS 2017 | TFS 2015 | TFS 2013

With the Code Coverage report, you can monitor how much code the team is testing over time. Team members can use this report to help determine how close parts of the code are to release quality. For information about how to access this report, see Excel reports.

Required Permissions

To view the report, you must be assigned or belong to a group that has been assigned the Read permissions in SharePoint Products for the team project.

To modify or customize the report, you must be a member of the TfsWarehouseDataReaders security role in SQL Server Analysis Services. You must also be assigned or belong to a group that has been assigned the Members permissions in SharePoint Products for the team project. For more information, see Grant Access to the Databases of the Data Warehouse for Team System.

Data in the Report

The team can review the Code Coverage report to determine whether tests cover the code sufficiently and how the coverage changed over time. As the following illustration shows, the report provides a line graph of the build verification test (BVT) code coverage and other coverage over the most recent four weeks.

This report is based on a PivotChart report that shows the most recent four weeks of data that was captured for code changes and that is stored in the data warehouse.

Required Activities for Tracking Code Coverage

For the Code Coverage report to be useful and accurate, team members must perform the following activities:

• Configure a build system. To use Team Foundation Build, you must set up a build system.

  For more information, see Build and Release agents.

• Create build pipelines. You can create several build pipelines and then run each of them to produce code for a different platform. Also, you can run each build for a different configuration.

  For more information, see Get started with CI/CD.

• Define tests to run automatically as part of the build. As part of the build pipeline, you can define tests to run as part of the build or to fail if the tests fail.

  For more information, see Set up continuous testing for your builds.

• Configure tests to gather code coverage data. For code coverage data to appear in the report, team members must instrument tests to gather that data.

• Run builds regularly. You can run builds at set intervals or after every check-in. You can create regular builds when you use the schedule trigger.

  For more information, see Build triggers.

  Note

  Although a team member can manually rate a build by using Build Explorer, this rating is not reflected in the Build Quality Indicators report. The build rating appears in the Build Summary report. For more information, see Rate the quality of a completed build and Build Summary.

Interpreting the Report

If the team practices test-driven development or similar techniques, the code coverage should almost always approach 100%. If unit tests are reused as BVTs, the code coverage should be visible in the Code Coverage report.

You can review the Code Coverage report to answer these questions:

• How much of the code is the team testing?

• Does the team have sufficient code coverage?

• Is code coverage increasing or decreasing over time?

  For more information about how code coverage impacts quality, see Quality and Build Quality Indicators.

Customizing the Report

You can customize the Code Coverage report by opening it in Office Excel and changing the filter options or a column field list for the PivotTable report. You can modify the report to support other views, as the following table describes.

Related articles

• Excel reports
• Design the layout and format of a PivotTable