Code coverage numbers are not accurate
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 205
Description
We've started adding Java Code Coverage numbers to PRs using the jacoco gradle plugin.
When we ran this in Maven, we got very low coverage reported for things like the Java SDK core. This was likely because we test the bulk of the SDK not in the SDK module, but in fact in the DirectRunner and other similar modules.
This is the still the case in gradle. So we'll need to make sure to watch for it.
This is a good "random improvement" issue for anyone to pick up.
Imported from Jira [BEAM-1399](https://issues.apache.org/jira/browse/BEAM-1399). Original Jira may contain additional context.
Reported by: dhalperi.
Contributor guide
Research direction
Start by tracing the Gradle JaCoCo configuration and how coverage is gathered across the SDK core, DirectRunner, and similar modules. Compare the Gradle results with the previously observed Maven behavior. Done means PR coverage numbers include the modules where the SDK's tests actually run and no longer report misleadingly low coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100