SonarQube is not reporting code coverage

SonarQube Server / Community Build
, ,
1

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube Server / Community Build, Scanner, Plugin, and any relevant extension)
  • how is SonarQube deployed: zip, Docker, Helm
  • what are you trying to achieve
  • what have you tried so far to achieve this

**Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

Hello All,
**
Merry Christmas and a very Happy New Year!
I am facing an issue where SonarQube is not reporting code coverage even though the coverage report (coverage/lcov.info) is successfully generated during the CI pipeline. The SonarQube analysis completes without errors, but the coverage remains at 0.0% on the dashboard.

The project uses Jest for test coverage in a JavaScript/React application. The lcov.info file exists, is non-empty, and contains valid data. The property sonar.javascript.lcov.reportPaths=coverage/lcov.info is configured correctly, and no warnings or errors appear in the scanner logs related to coverage import.

Despite verifying file paths, permissions, inclusion/exclusion rules, and ensuring the coverage file is present at scan time, SonarQube does not detect or import the coverage data.

Guidance is requested on debugging coverage import, known issues with Jest + SonarQube integration, or best practices for CI-based coverage detection.

SonarQube Server: Community Build v25.11.0.114957
Deployment: Docker Compose
Scanner: SonarScanner CLI
Language: JavaScript / React
Coverage Tool: Jest

Regards,
Harendra Singh

2

Hi Harendra,

Welcome to the community!

Can you post your analysis log?

The analysis / scanner log is what’s output from the analysis command. Hopefully, the log you provide - redacted as necessary - will include that command as well.

This guide will help you find them.

 
Thx,
Ann