You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Tyson Hamilton (Jira)" <ji...@apache.org> on 2020/05/26 15:06:00 UTC

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

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

Tyson Hamilton updated BEAM-1399:
---------------------------------
    Labels: beam-fixit newbie starter  (was: newbie starter)

> 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, 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)