Grouping coverage reports by module in multimodule projects

[AntipovAlexander]

Hi there!

First of all, thanks for creating and maintaining this amazing tool — it’s been a huge help!

I have a question regarding the organization of Kover reports in a multimodule application. My setup includes:

• An app module (acting as the merging module),
• Several library modules (feature modules).

At the moment, everything works perfectly, and I get a detailed coverage report, as shown in the screenshot below:

However, I was wondering if it’s possible to group the coverage results by module rather than displaying every single package. Specifically, I’d like to see a report where coverage is summarized at the module level, something like this (in HTML format, of course):

This kind of grouping would make the reports much cleaner and easier to analyze at a high level.

Is there any existing way to achieve this? Or perhaps a workaround that you could suggest?

Thanks in advance for your time and help!

[shanshin]

Hi,
unfortunately, at the moment it is not possible to generate a single HTML file with grouping by modules.

You can try to generate separate HTML files for each project, but this will complicate the configuration and increase the number of Gradle tasks.

kover {
    currentProject {
        // create variant named 'feature1' from based on release build variant
        copyVariant("feature1", "release")
    }

    reports {
        variant("feature1") {
            // show classes only for ':feature1' project
            filters.includes.projects.add(":feature1")
        }
    }
}

[shanshin]

Duplicate #272

[AntipovAlexander]

ok, thanks for your support!