Using Sonarqube 7.7 with latest sonar-maven-plugin Having a Maven multi-module structure like: a with property (<sonar.testExecutionReportPaths>${project.build.directory}/karma-reports/TEST-gui.Sonar.xml</sonar.testExecutionReportPaths>) b (this module contains the generic test execution repor…

Hi I’ll let Duarte decide about the logs, but it makes sense to go ahead with a reproducer. Thx, Ann

I confirm that this problem happens with version 7.9.1. The sonar.testExecutionReportPaths property is ignored when specified in the pom of a submodule. The log miss the any reference to “Sensor Generic Test Executions Report”. The property is taken in consideration when included in the main module…

Thanks for your confirmation. It’s really disappointing that this feature does not work at all. Any estimation when this will be fixed? Is there already an issue ticket created which can be linked here?

Looks like this is broken since 7.6 https://jira.sonarsource.com/browse/SONAR-11530

Hi, Thanks @reitzmichnicht for the detailed analysis of the issue. I have the exact same issue where I have a multi-module application made of React modules. I can generate an individual Generic Test Data report per module using jest-sonar-reporter in each module. But how can we make SonarQube 7…

@ganncamp any updates on this? Looks like this is a regression introduced in 7.6 which could be easily fixed.

As Andrea said, the sonar.testExecutionReportPaths is simply ignored when specified in the pom of a module. The only way to trigger the execution of the Generic Test Execution Sensor is to specify the property in the root pom. However, although the sensor executes, it will complain about not being …

BTW, the specs for the Generic Test Execution Report format ( https://docs.sonarqube.org/latest/analysis/generic-test/ ) says: Insert a file element for each test file. Its path attribute can be either absolute or relative to the root of the module. As we have seen here, this is definitely not…

Sorry, no updates on my side. Ann

Sadly I did not find any workaround yet for this problem.

GenericTestExecution does not work with maven multi-modules

SonarQube Server / Community Build

marcelstoer (Marcel Stör) September 17, 2021, 4:00pm 22

Connecting this to sonar.testExecutionReportPaths is not working at module level where this bug was discussed as well.

Topic		Replies	Views
sonar.testExecutionReportPaths is not working at module level SonarQube Server / Community Build scanner , modules , scanner-guild	6	7543	February 10, 2022
Generic test execution report doesn't find files in multi-module gradle SonarQube Server / Community Build sonarqube , scanner , coverage	7	326	April 22, 2024
sonar.testExecutionReportPaths not triggering the sensor when run from a gradle subproject SonarQube Server / Community Build sonarqube , gradle , scanner , scanner-guild	5	4782	April 30, 2021
Multi-module generic test execution report not picked up by scanner SonarQube Server / Community Build coverage , node , scanner-guild , unit-test , istanbul , bug-no-category	3	1636	June 8, 2021
Test Execution report for JavaScript not picked up SonarQube Cloud javascript , tests	7	4518	July 17, 2020

GenericTestExecution does not work with maven multi-modules

Related topics