Sonarqube is not showing code coverage after running

Question

I'm running sonarqube with maven.

I have installed it using following way. Using brew, I installed mysql and sonar.

When I run I get 7 critical bugs but the code coverage for 88 tests is zero

When I run it with IntelliJ's tools, I get the following results. (not zero!)

This is when I check Jacoco results directly. In $base_direc/target/jacoco/index.html

The same code when run with sonar-scanner

This is my maven configuration

My ~/.m2/settings.xml

Edit 1: I have found this in logs.

Edit2: I have edited ~/.m2/settings.xml added

<properties>
    <sonar.host.url>http://localhost:9000/</sonar.host.url>
</properties>

Edited /usr/local/Cellar/sonarqube/6.3.1/libexec/conf/sonar.properties added sonar.host.url=http://localhost:9000/

Edited /usr/local/etc/sonar-scanner.properties added - sonar.host.url=http://localhost:9000/

Ran the application in all above ways and the results were same, i.e, I could see Jacoco results but not in sonar.

Is it possible that if bugs are found sonar refuses to do code coverage?!

Anything relevant-seeming in your analysis log? If so, please [edit] your question to include that as well. — G. Ann - SonarSource Team, May 24 '17 at 11:50
@G.Ann-SonarSourceTeam I have found something and edited the question. Please check, is that helpful — Tarun Maganti, May 24 '17 at 12:44
is there anything related to the processing of the coverage reports? — G. Ann - SonarSource Team, May 24 '17 at 13:16

Tarun Maganti · Accepted Answer · 2021-11-25T08:53:08.527

24

I found the solution -

The maven plugin I have included has configuration of Jacoco's destfile and datafile as ${basedir}/target/coverage-reports/jacoco-unit.exec

but by default sonar reads at ${basedir}/target/jacoco.exec. I changed the default at http://localhost:9000/settings?category=java

Ref: Sonar Code Coverage

Couldn't find the working reference link. Here is aux link: Baeldung Sonar and jacoco

edited Nov 25 '21 at 08:53

answered May 25 '17 at 08:50

Tarun Maganti

3,076
2
35
64

2

Reference link is dead – coler-j Jun 18 '19 at 20:01
1

Life saver! Thank you for posting. – cadebe Feb 08 '20 at 21:28
Did you re-run sonarqube for the changes to take effect?? – Taranmeet Singh Dec 05 '21 at 14:12
I don't actually remember, it was 4.5 years ago. Please check the documentation. I tried looking for it, couldn't find. – Tarun Maganti Dec 05 '21 at 18:14

score 5 · Answer 2 · answered Mar 22 '19 at 08:07

I've resolved this by using the following steps:

1.To begin, I've add configuration in our pom.xml.

<properties>
  <sonar.core.codeCoveragePlugin>jacoco</sonar.core.codeCoveragePlugin>
  <sonar.jacoco.reportPath>${project.basedir}/../target/jacoco.exec</sonar.jacoco.reportPath>
  <sonar.language>java</sonar.language>
</properties>

2.In sonarqube properties file added the below part.

sonar.projectName=${JOB_NAME}
sonar.projectVersion=1.0.0
sonar.sources=src/main
sonar.sourceEncoding=UTF-8
sonar.language=java
sonar.tests=src/test
sonar.junit.reportsPath=target/surefire-reports
sonar.surefire.reportsPath=target/surefire-reports
sonar.jacoco.reportPath=target/jacoco.exec
sonar.binaries=target/classes
sonar.java.coveragePlugin=jacoco
sonar.verbose=true

I think the `sonar.jacoco.reportPath` was the missing piece of the puzzle for me. I wasted about 2 days at work trying to find this. Thank you. — Sridhar Sarnobat, Jan 25 '20 at 01:59

score 0 · Answer 3 · answered Nov 26 '19 at 06:31

I had same problem, I will help you to resolve that. Here 1st thing is to walk through your pom file.

<properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <java.version>1.8</java.version>
    <jacoco.version>0.8.5</jacoco.version>
    <sonar.jacoco.reportPath>target/jacoco-ut.exec</sonar.jacoco.reportPath>
    <sonar.jacoco.itReportPaths>target/jacoco-it.exec</sonar.jacoco.itReportPaths>
</properties>

In pom file, you used jacoco-ut.exec you have to use below properties on your execute SonarQube Scanner in Jenkins

sonar.java.binaries=target/classes
sonar.junit.reportsPath=target/surefire-reports
sonar.surefire.reportsPath=target/surefire-reports
sonar.jacoco.reportPath=target/jacoco-ut.exec

Keep in your mind about jacoco.exec in pom and property name of executing SonarQube Scanner in Jenkins

score 0 · Answer 4 · answered Feb 01 '22 at 07:05

For me, the issue was:
Reports are getting generated at pre-package phase. Now we updated Pull Request maven phase.
mvn -B clean test to mvn -B clean package.

Also, latest SONAR prefers XML report. You can specify path in maven pom via: <sonar.coverage.jacoco.xmlReportPaths>target/site/jacoco/jacoco.xml</sonar.coverage.jacoco.xmlReportPaths>

and in sonar project properties file:

sonar.projectKey=my-project
sonar.projectName=my-project

sonar.language=java
sonar.java.binaries=target/classes
sonar.sources=src/main
sonar.tests=src/test
sonar.exclusions=**/beans/*,**/config/*,**/constants/*,**/dtos/**,**/entity/*,**/exceptions/*,**/insights/*,**/App.java
sonar.sourceEncoding=UTF-8
sonar.dynamicAnalysis=reuseReports
sonar.junit.reportsPath=target/surefire-reports
sonar.java.coveragePlugin=jacoco
sonar.coverage.jacoco.xmlReportPaths=target/site/jacoco/jacoco.xml

Sonarqube is not showing code coverage after running

4 Answers4

1.To begin, I've add configuration in our pom.xml.

2.In sonarqube properties file added the below part.

Linked