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

Jacoco html, xml report exclusion rules does not work properly on 0.6.0 #220

Closed
k3marek opened this issue Aug 24, 2022 · 2 comments · Fixed by #225
Closed

Jacoco html, xml report exclusion rules does not work properly on 0.6.0 #220

k3marek opened this issue Aug 24, 2022 · 2 comments · Fixed by #225
Labels

Comments

@k3marek
Copy link

k3marek commented Aug 24, 2022

After fixing #201 the jacoco report still does not work as intended.
Note - with intellij engine everything is ok.

The jacoco report contains all of the possible packages for a given module. It does not change with class filters or with html filters.

Precisely, setting the class filters excludes exact coverage values from the report which results with 0% in the report.

Setup:

kover {
            ...
            filters {
                classes {
                    excludes.addAll(
                         "com.companyxyz.package.*",
                          "*.di.*"
                       )
                }
            }

Tried also to set

htmlReport {
                overrideFilters {
                    classes {
                        excludes.addAll(
                          "com.companyxyz.package.*",
                           "*.di.*"
                          )
                    }
                }
            }

but with no luck. The report contains all possible packages. The excluded ones shows simply 0% of coverage.
image

Am I doing something wrong with the jacoco setup?

@shanshin
Copy link
Collaborator

Hi,
when solving issue #201, I added filtering only to the instrumentation.
Now need to add a class-file filter for the JaCoCo reporter

@shanshin
Copy link
Collaborator

shanshin commented Oct 3, 2022

Fixed in 0.6.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants