Test: Publish Code Coverage Results

Last Update: 4/28/2017

Team Services | TFS 2017 | TFS 2015 | Previous versions: XAML Build, Release

icon Publishes the code coverage results of a build.


The build agent must have the following capabilities:

  • MSBuild
  • Azure PowerShell


Argument Description
Code Coverage Tool Required. The tool with which code coverage results are generated. Currently supported schemas are Cobertura and Jacoco.
Summary File Required. The path of the summary file containing code coverage statistics such as line, method, and class coverage. The value may contain minimatch patterns. Example: $(System.DefaultWorkingDirectory)/MyApp/**/site/cobertura/coverage.xml
Report Directory The path of the code coverage HTML report directory. The report directory is published for subsequent viewing as an artifact of the build. The value may contain minimatch patterns. Example: $(System.DefaultWorkingDirectory)/MyApp/**/site/cobertura
Additional Files The file path pattern specifying any additional code coverage files to be published as artifacts of the build. The value may contain minimatch patterns. Example: $(System.DefaultWorkingDirectory)/**/*.exec
Control options See Control options

More Information


I use Team Foundation Server on-premises and I don't see some of these features. Why not?

Some of these features are available only on Visual Studio Team Services and not yet available on-premises. Some features are available on-premises if you have upgraded to the latest version of TFS.

Help and support

  • Submit bugs through Connect

  • Send suggestions on UserVoice

  • Send a smile from the Send-a-Smile link on the menu bar.