Code coverage is showing 0

SonarQube Server / Community Build
1 
sonar.host.url=https://sonarqube.world-dev.franka.de

sonar.projectKey=fe:storefront-api

sonar.projectName=fe-storefront-api

sonar.projectVersion=1.0

sonar.javascript.lcov.reportPaths=src/platform/custom/coverage/lcov.info

sonar.exclusions=coverage/**,node_modules/**,report.xml

sonar.javascript.exclusions=**/test/**

sonar.sources=.

sonar.sourceEncoding=UTF-8

This is sonar properties file we are using , in the Log files I am seeing

**1:49:58** INFO: Analysing [/var/jenkins_home/workspace/build-webapp-api/repo/src/platform/custom/coverage/lcov.info] 
**11:49:58** WARN: Could not resolve 4 file paths in [/var/jenkins_home/workspace/build-webapp-api/repo/src/platform/custom/coverage/lcov.info] 
**11:49:58** WARN: First unresolved path: /var/jenkins_home/workspace/build-webapp-api/repo/src/platform/custom/test/cart.spec.js (Run in DEBUG mode to get full list of unresolved paths)

Can someone help me with this ?

2

Hi,

Welcome to the community!

I think we should probably sort out your analysis parameters before we get to the coverage reports.

This property expects paths or patterns that describe paths to files. What you’ve specified doesn’t include the final, file part. The ** means “0-n directories”. For the first two, I’m guessing you meant:
coverage/**/*.*,node_modeules/**/*.*

This assumes that coverage and node_modules exist in your project root…? For the third value, what you’ve specified indicates that report.xml also exists in project root…?

This property doesn’t actually exist. I guess you’re trying to make sure that your test files aren’t analyzed as source code? In that case, I would recommend an addition to your list of sonar.exclusions: **/test/**/*.js

Doing that may sort out this error, since the ‘missing’ file seems to actually be a test file…?

So, can you make these changes and see if the results are any better?

 
Ann

4

Sure , Let me try the mentioned steps.

5

Thanks that’s fixed the issue, code coverage started showing now , however we are still seeing the warn

INFO: Analysing [/var/jenkins_home/workspace/build-webapp-api/repo/src/platform/custom/coverage/lcov.info] 18:24:23 WARN: Could not resolve 4 file paths in [/var/jenkins_home/workspace/build-webapp-api/repo/src/platform/custom/coverage/lcov.info] 18:24:23 WARN: First unresolved path: /var/jenkins_home/workspace/build-webapp-api/repo/src/platform/custom/test/cart.spec.js (Run in DEBUG mode to get full list of unresolved paths)

6

Hi,

You can turn on debug logging to see what those 4 paths are. But from the first path, it looks like your coverage report includes test coverage of tests…

 
Ann

7

I would also love to know which parameter Define the amount to Lines to cover , is that the Unit Test cases written. I am new to sonarqube and would like to know more about the way the coverage works.

As I told I can see the coverage coming but only 22% is shown , I need to know why its knot covering fully. Can you suggest some good documentation to Read.

8

Hi,

Lines to cover isn’t defined by a parameter. For the files included in your coverage report, we use what the report provides. For the files omitted from your coverage report, we calculate executable lines.

This blog may also help.

 
Ann

9

Is there any chance can I setup a Meeting with you to discuss further about this issue ?

10

In one of our other project the sonar properties file looks like this

sonar.host.url=https://sonarqube.world-dev.franka.de

sonar.projectKey=fe:storefront-shop

sonar.projectName=fe-storefront-shop

sonar.sources=.

What modifications you suggest to add to do start coverage

11

Hi,

The docs should help.

 
Ann

12

do we need to have lcov file to get the coverage information ?

13

Hi,

Prior to analysis, you need to produce a coverage report to feed in to analysis.

 
HTH,
Ann

14

Okay got it so basically a coverage report needs to be created before doing sonar scan.

1 Like