We only recommend the use of this tool when the build agent has Visual Studio Enterprise installed or when you are using an Azure DevOps Windows image for your build. Just after the build step but before the scanner end step, ensure that your test step produces the coverage report file.Įxamples using the.

In the scanner begin step, add the appropriate parameter to specify the location of the coverage report file that will be produced.To enable coverage reporting, you need to make the following changes: In between, you perform the actual build and your tests. The analysis is always split into two parts in your build process

Sections for details), but the essential steps are the same. The setup is slightly different for each variant NET tool and SonarQube Extension for Azure DevOps). NET scanner comes in four variants depending on which version of. In this section, we discuss the directly supported tools.įor information on the generic format, see Generic Test Data. (though you will have to convert its output to the generic format yourself). NET test coverage tools:Īdditionally, a generic coverage format is also supported if you wish to use an unsupported tool You then need to configure your analysis to tell the SonarScanner where the report is located so that it can pick it up and send it to SonarQube, where it will be displayed on your project dashboard along with the other analysis metrics. Instead, you must set up a third-party tool to produce the report as part of your build process. However, SonarQube does not generate the coverage report itself. SonarQube supports the reporting of test coverage information as part of the analysis of your.

Visual studio code coverage not working