-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add profile for coverage reports with JaCoCo #283
Comments
kwin
changed the title
Add profile for Coverage reports with JaCoCo
Add profile for coverage reports with JaCoCo
Dec 20, 2024
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
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.xml
target/site/jacoco-it/jacoco.xml
build/reports/jacoco/test/jacocoTestReport.xml
TODO: 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: