[jira] [Commented] (BEAM-1399) Code coverage numbers are not accurate

["Tibor Kiss (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904977#comment-15904977 ] 

Tibor Kiss commented on BEAM-1399:
----------------------------------

The Python-SDK's coverage numbers are also not included in the coveralls report.
Created a separate tracking jira (as a subtask of to the UT-related uber-jira) for that effort: BEAM-1685

> 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
>              Labels: newbie, starter
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)