Skip to content
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

OBPIH-6649 Add support for Jacoco code coverage reporting #4933

Merged
merged 3 commits into from
Nov 12, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
stop filtering out closures in jacoco report
  • Loading branch information
EWaterman committed Nov 12, 2024
commit bfce1a4246cf2c46b568bbf25484276415e9e002
6 changes: 3 additions & 3 deletions build.gradle
Original file line number Diff line number Diff line change
Expand Up @@ -852,9 +852,9 @@ jacoco {
// Note that the paths here are by package name (as they are in "build/classes/groovy/main"). As such, we cannot
// filter by Grails folders such as "**/controller/**" (but we could filter by "**/*Controller.class").
List jacocoExcludes = [
// Filter out the Groovy-generated closure classes from Jacoco for the sake of visual clarity in the report.
// https://stackoverflow.com/questions/39453696/how-do-you-exclude-implicit-groovy-closure-classes-from-jacoco-test-resport-with
'**/*$*_closure*',
// This filters out all the Groovy-generated closure elements from Jacoco, which helps de-clutter the report but
// also prevents any closures from being counted in the report. Leave them in to get a more accurate percentage.
//'**/*$*_closure*',
]
jacocoTestReport {
// Makes sure that tests are always run before a report is generated (because otherwise the report will be blank or
Expand Down
Loading