0 Percent Code Coverage

[bthomason (Brian Thomason)]

Two days ago in one of our projects SonarCloud has started to report back 0% code coverage on new code. This is causing our quality gate to fail in our PR. We have tried many different configuration options as well as updating libraries to see if something changed on our end to cause this to happen. Nothing seems to be changing the outcome. I was able to output the coverage report to the pipeline and that coverage report says the new code we changed has 100% coverage, however SonarCloud still reports back 0%.

Below is the command we are using for the sonarcloud scanner. We’ve verified this command is similar to another projects command which is not reporting 0% coverage.

sonar.exclusions=**/*.js,**/node_modules/**,**/*.html
sonar.typescript.lcov.reportPaths=vsts-tasks/Tasks/ReleaseDefinitionValidator/coverage/lcov.info
sonar.pullrequest.base=master
sonar.test.inclusions=vsts-tasks/Tasks/ReleaseDefinitionValidator/tests/**/*.ts

Below is an image showing the output of the coverage report. Specifically the files that have new code in them.

I’m wondering if you would be able to help us get this resolved so that our coverage is reporting correctly in SonarCloud.

[Peeter_Piegaze]

Hi Brian,

The problem may be related yout the analysis scoping you have configured. Have a look here and see if re-doing your scoping parameters helps:

How do SonarCloud properties work in relation to each other?

Hello all, I’m new to SonarCloud and just wanted a little further clarification on how the properties listed in the sonar-project.properties file works. In particular, how does sonar.tests work in relation to sonar.test.inclusions. We came across an issue with the coverage that we fixed but we’re not 100% sure why that fixed it. Here is an example. We have the following directory structure: src/[feature]/components src/[feature]/utils src/[feature]/test src/[feature]/index.ts When we incl…

[bthomason (Brian Thomason)]

Hi Peeter,

I forgot to update this, but we were able to fix this issue simply by changing our reportPaths from typescript to javascript. It is odd that this change is required because just a couple days prior this post the above configurations were working fine. In addition we have had to modify multiple other repositories from using typescript in the reportPaths to javascript. So our new working configuration is the following

sonar.exclusions=**/*.js,**/node_modules/**,**/*.html
sonar.typescript.lcov.reportPaths=vsts-tasks/Tasks/ReleaseDefinitionValidator/coverage/lcov.info
sonar.pullrequest.base=master
sonar.test.inclusions=vsts-tasks/Tasks/ReleaseDefinitionValidator/tests/**/*.ts