# PR showing 0% code coverage, yet jacoco.xml file exists **URL:** \ **Category:** SonarQube Server / Community Build\ **Tags:** sonarqube, coverage\ **Created:** [August 22, 2022, 9:25pm UTC](https://community.sonarsource.com/t/pr-showing-0-code-coverage-yet-jacoco-xml-file-exists/70217 "2022-08-22T21:25:55Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [August 23, 2022, 8:14am UTC](https://community.sonarsource.com/t/pr-showing-0-code-coverage-yet-jacoco-xml-file-exists/70217/2 "2022-08-23T08:14:02Z")
Hey there. You haven’t given us much information to go on. What build tool are you using? What do the scanner logs say? In any case, I recommend starting at this guide: > [@\[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/pr-showing-0-code-coverage-yet-jacoco-xml-file-exists/70217)._