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

Support for Gradle JVM Test Suite Plugin #298

Closed
a-glapinski opened this issue Jan 30, 2023 · 1 comment
Closed

Support for Gradle JVM Test Suite Plugin #298

a-glapinski opened this issue Jan 30, 2023 · 1 comment
Assignees
Labels
Feature Feature request issue type S: untriaged Status: issue reported but unprocessed

Comments

@a-glapinski
Copy link

It would be nice to be able to aggregate the results of multiple code coverage reports for each test suite from the JVM Test Suite Plugin. The JaCoCo Report Aggregation Plugin
does exactly that - when the JVM Test Suite plugin is applied, [testSuite]CodeCoverageReport tasks are added for each test suite.

Also, not sure if it is related to #284, but IMO it would be nicer that instead of creating merged report for all subprojects of the given project, the Kover plugin would work in the similar fashion as the Test Report Aggregation Plugin and the JaCoCo Report Aggregation Plugin - only the direct and transitive project dependencies of the current project’s runtime classpath are selected for potential aggregation (sample from Gradle docs).

@a-glapinski a-glapinski added Feature Feature request issue type S: untriaged Status: issue reported but unprocessed labels Jan 30, 2023
@shanshin
Copy link
Collaborator

shanshin commented Apr 21, 2023

Hi,
since the Kover is a universal plugin used for both Kotlin/JVM, Kotlin/MP and Kotlin/Android projects, integration with a plugin specialized for Java projects is difficult and may not be convenient.

Based on this, there are no plans to integrate Kover with the JVM Test Suite Plugin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Feature request issue type S: untriaged Status: issue reported but unprocessed
Projects
None yet
Development

No branches or pull requests

2 participants