Add profile for coverage reports with JaCoCo #283
Comments
kwin
changed the title
|
Also note jacoco/jacoco#1676. |
kwin
added a commit
that referenced
this issue
Dec 21, 2024
Add dedicated profile "coverage" to generate separate reports for both UTs and ITs. This closes #283
kwin
added a commit
that referenced
this issue
Dec 21, 2024
Add dedicated profile "coverage" to generate separate reports for both UTs and ITs. This closes #283
kwin
added a commit
that referenced
this issue
Dec 21, 2024
Add dedicated profile "coverage" to generate separate reports for both UTs and ITs. This closes #283
|
There was strong resistance in the PR, therefore closing as won’t fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The defacto standard for code coverage calculation with Maven/Java is JaCoCo. A profile should be provided in the ASF parent which collects coverage data for both UTs/ITs and creates reports as outlined in https://www.eclemma.org/jacoco/trunk/doc/examples/build/pom-it.xml.
Those reports should be usable also for https://docs.sonarsource.com/sonarqube-server/10.7/analyzing-source-code/test-coverage/java-test-coverage/ (i.e. be emitted with default filenames) or https://github.com/codecov/example-java-maven
Default locations for
sonar.coverage.jacoco.xmlReportPaths(can be overridden) aretarget/site/jacoco/jacoco.xmltarget/site/jacoco-it/jacoco.xmlbuild/reports/jacoco/test/jacocoTestReport.xmlTODO: Check if SonarQube supports separate reports for ITs and UTs or requires them in merged format.
The text was updated successfully, but these errors were encountered: