Sonarcloud says I have 0% Code coverage even though I wrote unit tests

[dougnoel (Doug Noël)]

• ALM used (GitHub)
• CI system used (GitHub Actions)
• Languages of the repository (Java)
• Only if the SonarCloud project is public, the URL https://sonarcloud.io/dashboard?id=dougnoel_sentinel
  • And if you need help with pull request decoration, then the URL to the PR too https://github.com/dougnoel/sentinel/pull/194/checks?check_run_id=2082531654

I am using SonarCloud with GitHub Actions. I turned it on last night and was resolving bugs today. When I pushed a branch and did a PR it failed because there are no new unit tests. I in fact made unit tests and there are other unit tests in the project, but none of them are getting recognized. I am just using the default settings given for setting up SonarCloud with GitHubActions. Did I not configure something? Any help would be appreciated.

[Peeter_Piegaze]

Hi Doug. Welcome to the community!

SonarCloud does not automatically run your tests or compile coverage reports itself. It has to import those reports from a coverage analysis that you set up separately. In your case (a Java project) you would use the Jacoco library and the associated Jacoco maven plugin.

For details, have a look here:

JaCoCo import troubleshooting

This guide will help you diagnose and resolve issues related to JaCoCo coverage import on SonarQube/SonarCloud. Principles apply to all sorts of coverage reports, though there are few caveats specific to JaCoCo. Problems you have Your coverage displays 0%? It dropped after a SonarQube upgrade? You had a coverage value on the project Dashboard and suddenly nothing? Your coverage is really low compared to what is expected? Figures don’t match between JaCoCo and what’s reported by SonarQube? ​…

[Coverage & Test Data] Importing JaCoCo coverage report in XML format

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…

[dougnoel (Doug Noël)]

Oh hey thanks, I figured that out eventually. Just saw you replied. I had found those articles but they didn’t help completely. After digging around, I found that I had to pass the following in the Actions yaml file: mvn -B org.jacoco:jacoco-maven-plugin:prepare-agent verify org.jacoco:jacoco-maven-plugin:report org.sonarsource.scanner.maven:sonar-maven-plugin:sonar

For some reason every help file I found assumed either I knew that, or that just putting the info in the pom file would make them execute. Maybe I’m missing something, but that command made it work for me so I’m posting it here for anyone who comes after me.

Thanks!