# SonarQube Code Coverage always shows 0%

**URL:** <https://community.sonarsource.com/t/sonarqube-code-coverage-always-shows-0/98550>\
**Category:** SonarQube Server / Community Build\
**Tags:** coverage\
**Created:** [September 4, 2023, 5:58am UTC](https://community.sonarsource.com/t/sonarqube-code-coverage-always-shows-0/98550 "2023-09-04T05:58:30Z")\
**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:** [September 5, 2023, 7:40am UTC](https://community.sonarsource.com/t/sonarqube-code-coverage-always-shows-0/98550/2 "2023-09-05T07:40:27Z")

</div>

Hey there.

I think this guide should help you, including the section on **Troubleshooting** :

> [@\[Coverage & Test Data\] Importing JaCoCo coverage report in XML format](https://community.sonarsource.com/t/coverage-test-data-importing-jacoco-coverage-report-in-xml-format/12151):
>
> Importing JaCoCo coverage report in XML format Version 5.12 of our SonarJava analyzer deprecated uses JaCoCo’s binary format (.exec files) to import coverage. This binary format is internal to the JaCoCo project, and as such there are no guarantees for backward compatibility, so it should not be used for integration purposes. As a replacement, when you scan a project with Sonar scanner, we use a special Jacoco report analyzer, which imports your JaCoCo’s XML coverage report, and this is the pr…

---

_[View the full topic](https://community.sonarsource.com/t/sonarqube-code-coverage-always-shows-0/98550)._