# Jacoco & Sonarqube Coverage doesn't match

**URL:** <https://community.sonarsource.com/t/jacoco-sonarqube-coverage-doesnt-match/95152>\
**Category:** SonarQube Server / Community Build\
**Tags:** jacoco, java, coverage\
**Created:** [July 5, 2023, 6:01am UTC](https://community.sonarsource.com/t/jacoco-sonarqube-coverage-doesnt-match/95152 "2023-07-05T06:01:58Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [July 5, 2023, 10:01am UTC](https://community.sonarsource.com/t/jacoco-sonarqube-coverage-doesnt-match/95152/2 "2023-07-05T10:01:56Z")

</div>

I suggest finding a specific discrepancy between the report (a file, for example) and sharing the information (screenshots, information).

Also take a look at this guide:

> [@JaCoCo coverage is different in Sonar](https://community.sonarsource.com/t/jacoco-coverage-is-different-in-sonar/35757):
>
> Problem you have Your JaCoCo coverage is not the same on SonarQube/SonarCloud than it is on JaCoCo Check the following It might be expected because you are not looking at the right metrics. Read more about this in the [SonarQube and code coverage](https://community.sonarsource.com/t/sonarqube-and-code-coverage/4725) guide. Your project has more than only Java/Kotlin/Scala code so when aggregated, coverage results might differs than only Java code coverage. If you are using Lombok, make sure that you have the right configuration using the [Getting meaningful covera…](https://community.sonarsource.com/t/getting-meaningful-coverage-results-in-sonarqube-when-using-jacoco-and-lombok/13821)

---

_[View the full topic](https://community.sonarsource.com/t/jacoco-sonarqube-coverage-doesnt-match/95152)._