Troubleshooting code coverage

Troubleshooting

Knowing where to begin looking for information is the first step to reaching out for help. Most commonly found problems have already been solved and their answers can be found on a Sonar Community Forum channel dedicated to your product (SonarLint, SonarCloud, and SonarQube).

See below for an overview of community guides written for .NET projects and a short list of some known issues.

Community guides

• [Coverage & Test Data] Generate Reports for C#, VB.net: Get up to speed on how to import code coverage for your .NET project.
• [Coverage] Troubleshooting guide for .NET code coverage import: The most frequent problems regarding code coverage import, each with suggested solutions.
• Finding logs about importing code coverage: Does your coverage data look wrong? Check the scanner logs first; here you’ll find details to investigate what each sensor has done during the import.
• Investigating the performance of your .NET analysis: This guide provides an introduction to what is happening in the analysis to guide your investigation and contains ten steps you can take to improve the performance of your analysis.

Other possible problems

No coverage information for .NET Core reports

Description: Your code coverage is correctly configured for a .NET Core project and the scanner finds and processes the coverage reports, but no coverage information is shown in SonarQube or SonarCloud.

Possible causes: VSTest issue 800: Code coverage requires DebugType full.

Possible solution: Check that the DebugType property is set to Full in the project file.