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
Hello! I use kover in multimodule android project for generating reports for single modules and for the whole project (aggregated project report). The project contains both Android and JVM submodules.
When I run :koverHtmlReport, I get the aggregated HTML report with only filtering rules from root build.gradle. But specific rules from the subprojects' build.gradle are ignored. Is it expected behavior?
Kover 0.8.0
The text was updated successfully, but these errors were encountered:
tonykolomeytsev
changed the title
Module-specific report filters are ignored in aggregated project report
Module-specific report filters are ignored in merged project report
Jun 5, 2024
The block kover { reports { ... } } configures only those Kover tasks that are located in the same module in which this config is specified.
So, if you specify filters in the root project, then these filters will affect only the result of the :koverHtmlReport task, if you specify filters in subproject child, then of the :child:koverHtmlReport task, etc.
If you are using the root project to aggregate coverage reports (create a merged report), then you need to configure the block kover { reports { ... } }only in the root project.
Hello! I use kover in multimodule android project for generating reports for single modules and for the whole project (aggregated project report). The project contains both Android and JVM submodules.
When I run
:koverHtmlReport
, I get the aggregated HTML report with only filtering rules from rootbuild.gradle
. But specific rules from the subprojects'build.gradle
are ignored. Is it expected behavior?Kover 0.8.0
The text was updated successfully, but these errors were encountered: