Discrepancy in Code Coverage - SonarCloud Dashboard

Template for a good new topic, formatted with Markdown:

  • ALM used Azure DevOps
  • CI system used Azure DevOps
  • Scanner command used when applicable (private details masked)
  • Languages of the repository Javascript

We Observe there is a discrepancy in the code coverage showing from local scan to the Sonar results. Our team is using Mocha Chai for the Unit testing.

Need help in understanding if there is any configuration changes need to be done from our end.

Please Suggest.

Hey there.

What’s the discrepancy (no coverage reported, some coverage reported, some specific files completely missing coverage)? What do the scanner-side logs say about the import of your coverage report? There’s not much to go off of here.