Coverage stays at 0.0% even though SonarScanner seems to properly process it

SonarCloud
, , , ,
1

We have been trying to report test coverage to SonarCloud using our github actions. We’ve followed your documentation regarding setting up test coverage reporting using dotCover ([Coverage] Troubleshooting guide for .NET code coverage import).

Everything seems to be working and processed by sonarscanner. However it (and every variation we tried) won’t end up in SonarCloud report for the pull request. We’ve also closely checked every step in the troubleshooting guide on your community forums ([Coverage] Troubleshooting guide for .NET code coverage import).

Scherm­afbeelding 2023-11-15 om 15.46.45
Scherm­afbeelding 2023-11-15 om 15.46.451396×372 188 KB

Scherm­afbeelding 2023-11-15 om 15.40.21
Scherm­afbeelding 2023-11-15 om 15.40.21919×318 23.6 KB

We’ve really tried everything we could find in the documentation and on the community forums but nothing seems to work. Could it be that there is an issue on the side of SonarCloud? Otherwise could you please help us try to find the issue.

I have got a lot of debug information but can’t not share this in the public community because of company policy. We can share it but not publicly.

  • Github actions workflow file
  • Github run logs (including verbose sonarscanner output)
  • The generated testreport html files
2

Hey there.

  • It looks like this is in the context of PR analysis – is it the same on your main branch analysis?
  • Can you provide a screenshot of your project dashboard, including where it does (or doesn’t) show coverage?
3

Hi Colin,

It’s indeed in the context of a PR. The github action running dotCover and publishing to sonarcloud doesn’t run in the main branch yet as it’s not working for the PR yet.

Here’s the screenshot of the sonarcloud dashboard showing the 0% coverage.

Scherm­afbeelding 2023-11-21 om 08.14.00
Scherm­afbeelding 2023-11-21 om 08.14.001957×759 59.5 KB

I would be happy to share logs, github action configuration and the generated reports but I can’t do that publicly.

4

Thanks.

Here it looks like the coverage is being properly processed because it shows the 85.8% Estimated after merge figure.

The reason you don’t see any other information is that there are 0 new lines in the pull request. So there’s nothing to be covered.

What is the context of this pull request? Do you expect to see changed lines of code (not just property files)?

5

The pull request indeed just contains the configuration for reporting the test coverage.

It was my understanding that it will display the full coverage percentage. So the reported coverage on a pull request only applies only to the newly added lines? And then the “estimated coverage after merge” is the full code coverage for the entire codebase?

Our intended use case was to also guard for a lowering overall coverage, which is something that could happen when tests are modified.

6

That’s correct.

We get that a lot! We don’t have a great answer today.