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

Fixed the presence of classes instrumented with Robolectric in Jacoco reports #541

Merged
merged 1 commit into from
Feb 15, 2024

Conversation

shanshin
Copy link
Collaborator

@shanshin shanshin commented Feb 14, 2024

It seems that after Robolectric instrumentation, source locations are lost and JaCoCo does not instrument such classes by default. There is a need to change the flag to disable this behavior.

After changing this flag, errors occur in the instrumentation of JVM classes (because they were previously excluded due to the lack of sources). The package with these classes was determined empirically.

Fixes #530

… reports

It seems that after Robolectric instrumentation, source locations are lost and JaCoCo does not instrument such classes by default. There is a need to change the flag to disable this behavior.

After changing this flag, errors occur in the instrumentation of JVM classes (because they were previously excluded due to the lack of sources). The package with these classes was determined empirically.

Fixes #530
@shanshin shanshin changed the title Fixed the presence of classes instrumented with Robolectric in Jacoco… Fixed the presence of classes instrumented with Robolectric in Jacoco reports Feb 14, 2024
@shanshin shanshin merged commit f0d57ca into main Feb 15, 2024
1 check passed
@shanshin shanshin deleted the jacoco-fix branch February 15, 2024 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Kotlin test coverage not reported for Java production code with JaCoCo
2 participants