You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi - Is there an option to update file path in the report ?
As a part of the drop of modules on the SonarQube side (https://jira.sonarsource.com/browse/MMF-365) in SonarQube v7.6, the generic coverage/test reports sensors were changed to be global sensors (https://jira.sonarsource.com/browse/SONAR-11530), meaning they only run once for the project (and not for each module). To address this, we need to provide the paths to all generic execution reports to sonar.testExecutionReportPaths at the root level of the project. In the case of a multi-module project, we have the generic test report using this karma-sonarqube-reporter being generated inside a javascript module and the file path of the test files inside the results xml file is all relative to that module. This does not work.
These test file paths need to be relative to the root folder or absolute file paths, otherwise the generic test execution sensor running at the root level is unable to recognize these files.
The text was updated successfully, but these errors were encountered:
Hi @msainath4 thank for your question. Unfortunately, the current version doesn't support customizing test paths. Do you think a callback function could help you to accomplish that. We could use it to redefine the test path on the fly. If you think so, I can help you on implementing this new feature and sending a PR.
peteyoungs
pushed a commit
to peteyoungs/karma-sonarqube-reporter
that referenced
this issue
Apr 1, 2022
Hi - Is there an option to update file path in the report ?
As a part of the drop of modules on the SonarQube side (https://jira.sonarsource.com/browse/MMF-365) in SonarQube v7.6, the generic coverage/test reports sensors were changed to be global sensors (https://jira.sonarsource.com/browse/SONAR-11530), meaning they only run once for the project (and not for each module). To address this, we need to provide the paths to all generic execution reports to sonar.testExecutionReportPaths at the root level of the project. In the case of a multi-module project, we have the generic test report using this karma-sonarqube-reporter being generated inside a javascript module and the file path of the test files inside the results xml file is all relative to that module. This does not work.
These test file paths need to be relative to the root folder or absolute file paths, otherwise the generic test execution sensor running at the root level is unable to recognize these files.
The text was updated successfully, but these errors were encountered: