[ 
https://issues.apache.org/jira/browse/BEAM-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kenneth Knowles updated BEAM-1399:
----------------------------------
    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.

  was:
We've started adding Java Code Coverage numbers to PRs using the jacoco plugin. 
However, we are getting very low coverage reported for things like the Java SDK 
core.

My belief is that this is happening because we test the bulk of the SDK not in 
the SDK module , but in fact in the DirectRunner and other similar modules.

JaCoCo has a {{report:aggregate}} target that might do the trick, but with a 
few minutes of playing with it I wasn't able to make it work satisfactorily. 
Basic work in https://github.com/apache/beam/pull/1800

This is a good "random improvement" issue for anyone to pick up.


> 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: Daniel Halperin
>            Priority: Major
>              Labels: newbie, 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
(v7.6.3#76005)

Reply via email to