Sonar way profile caused drop in code coverage

Repo code coverage scan is incorrect.
Change to the sonar way profile on Jan 15th caused this.

When run locally in an IDE, the coverage is correct.

Welcome to the community!

The correlation is interesting. I think we don’t have enough details to call it cause just yet.

The code coverage data you see in SonarCloud comes from the coverage reports it processes. If you think the coverage is incorrect, you need to track it down to its source. For example:

  • Pick a file for which SonarCloud shows coverage that looks incorrect to you
  • Find that file in the coverage report, check if it matches what you see in SonarCloud
  • If doesn’t match, then verify that the coverage report file is actually processed when you scan the project (look in the scanner output)

Hi Janos,

Thanks for getting back to me.
I have run it locally towards a docker sonarcloud and got similar results. ~50% line coverage.
I still cannot figure out why the coverage has dropped.

It is a very small project and nothing changed in terms of code around that date - Jan 15th.;a=shortlog;h=refs%2Fheads%2Fmaster

Was there a sonarcloud docker image released as part of the change in sonar way profile update?
Maybe I can run that image version -1 to check the diff.