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

Different behaviour between Kover & JaCoCo coverage tools #666

Closed
bilousovam opened this issue Aug 7, 2024 · 2 comments · Fixed by #668
Closed

Different behaviour between Kover & JaCoCo coverage tools #666

bilousovam opened this issue Aug 7, 2024 · 2 comments · Fixed by #668
Assignees
Labels
Bug Bug issue type S: ready for release Status: merged in the main branch

Comments

@bilousovam
Copy link

bilousovam commented Aug 7, 2024

When I use Kover without Jacoco I have information about line coverage:
Task :app:koverPrintCoverageDevRelease :app line coverage: 18.0846%
But when I add:
kover { useJacoco() }
I always get:
Task :app:koverPrintCoverageDevRelease :app line coverage: 0% [ant:jacocoReport] Rule violated for bundle :app: lines covered ratio is 0.0000, but expected minimum is 1.0000

I try to use filters but it wasn't help. It isn't work with filters and without one.

Environment:
Kover Gradle Plugin version: 0.7.6 and 0.8.3
Gradle version: 8.1
Kotlin project type: Kotlin/Android
Coverage Toolset: Kover, JaCoCo

@bilousovam bilousovam added Bug Bug issue type S: untriaged Status: issue reported but unprocessed labels Aug 7, 2024
@shanshin
Copy link
Collaborator

shanshin commented Aug 7, 2024

Hi,
it's known issue #544.

Until #630 is implemented, ignore this message for koverPrintCoverage... tasks

@shanshin shanshin reopened this Aug 28, 2024
@shanshin shanshin added S: ready for release Status: merged in the main branch and removed S: untriaged Status: issue reported but unprocessed labels Aug 28, 2024
@shanshin
Copy link
Collaborator

shanshin commented Sep 3, 2024

Fixed in 0.9.0-RC

@shanshin shanshin closed this as completed Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Bug issue type S: ready for release Status: merged in the main branch
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants