[
https://issues.apache.org/jira/browse/BEAM-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132070#comment-17132070
]
Beam JIRA Bot commented on BEAM-1399:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Code coverage numbers are not accurate
> --------------------------------------
>
> Key: BEAM-1399
> URL: https://issues.apache.org/jira/browse/BEAM-1399
> Project: Beam
> Issue Type: Bug
> Components: build-system, sdk-java-core, testing
> Reporter: Dan Halperin
> Priority: P2
> Labels: beam-fixit, newbie, stale-P2, starter
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
