New lines not covered for Pull request

SonarCloud
, ,
1

Hi,

I am getting “0.00% coverage on new code” ( 284 new lines are there) on sonar cloud for PR analysis. can you please tell me how do enable coverage for pr. We are already passing below variables in my pipeline script:

// Set specific variables for PR (pull request)
    if (typeJob == "multiBranchPR") {
        commonSonarGate["parametersSonarCloud"]["-Dsonar.pullrequest.branch"] = CHANGE_BRANCH
        commonSonarGate["parametersSonarCloud"]["-Dsonar.pullrequest.key"] = CHANGE_ID
        commonSonarGate["parametersSonarCloud"]["-Dsonar.pullrequest.base"] = CHANGE_TARGET

related sonarproperties in sonar-project.properties file

sonar.test.inclusions=src/**/*.spec.ts
sonar.ts.tslintconfigpath=tslint.json
sonar.exclusions=src/**/*.model.ts,src/**/*.spec.ts,src/**/*.mock.ts,src/**/*.js
sonar.coverage.exclusions=src/**/*.spec.ts,src/**/*.mock.ts,src/**/*.js
sonar.typescript.lcov.reportPaths=coverage/lcov.info

sonar cloud ui tab: on new code → converage:-

image
image715×598 23 KB

image
image877×420 31.6 KB

image
image1399×362 12.8 KB

2

Hi,

Please do not ping people by name on new posts. I removed them now.

Common problems with missing test coverage:

  • Was the test coverage report file properly imported by the scanner? Please inspect the scanner output, look for lines mentioning “coverage”.
    • If your test report file does not appear anywhere, there are several possibilities
      • Are the report files present in the filesystem at the paths you specified? Please verify.
      • Have you used the correct scanner parameter names to specify the report paths. If there’s a typo, the scanner will not understand your intent.
    • If the scanner output mentions some error about the importing a coverage report, it usually explains an action you need to take to fix the problem. If the action is not clear, you can ask us by providing the message.
  • If the coverage report was correctly imported, but some lines that you think should be covered are in fact not covered, then please check that those files and lines are actually in the report file.

Let me know what you find, and we can proceed from there.

1 Like
4

Hi @janos
I see below out from my jenkins build.

image
image1151×314 32.9 KB

5

Hi @janos
I see below warning in jenkins console output:
WARN: Could not find ref: develop in refs/heads, refs/remotes/upstream or refs/remotes/origin

image
image848×201 20 KB

6

Please post log lines as text in the future, not as images. That way we can easily point out and talk about specific lines.

The message you highlighted tells you that no file was imported. The line before that tells you the locations where the files were expected. You need to make sure the files are actually there, or set the indicated property to the correct path.

The next screenshot points out that the Git ref of your analysis (probably the base branch of the pull request) could not be found by Git. You need to add a git fetch origin the-base-branch-name so that it’s fetched.