Frontend JavaScript coverage is 0% after SonarQube upgrade in multi-module Maven project

SonarQube Server / Community Build
, , ,
1

We have a multi-module Maven project with backend (Java + JaCoCo) and frontend (React + Jest).

Backend coverage is reported correctly, but frontend JavaScript coverage is always 0% after upgrading SonarQube.

Project structure:

image
image402×156 4 KB

The LCOV file is generated at:
fcs-react-web/frontend/coverage/lcov.info

The frontend POM contains:
sonar.javascript.lcov.reportPaths=coverage/lcov.info

Sonar is triggered using:
mvn -f fcs/pom.xml verify sonar:sonar

This setup worked before the upgrade. Tests run successfully and coverage files exist.

Sonar version: 2025.5

What is the correct way to make SonarQube pick up frontend JavaScript coverage in a multi-module Maven setup?

2

Hi,

Welcome to the community!

Are you specifying the sonar.maven.scanAll property?

You say you started seeing this after upgrading your SonarQube instance. What version did you upgrade from?

 
Thx,
Ann

3

Hi Ann,
Have included sonar.maven.scanAll property as well, still frontend coverage has not appeared. SonarQube version upgraded from 2025.4.2 to 2025.5.0.

4

Hi,

Did you also upgrade your scanner at the same time, or just the server? Can you provide a debug 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.

 
Ann