You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Udi Meiri (Jira)" <ji...@apache.org> on 2020/08/10 21:35:00 UTC

[jira] [Commented] (BEAM-2762) Coverage report for Python code

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

Udi Meiri commented on BEAM-2762:
---------------------------------

PR 12257 will add coverage collection, but it won't be pushed to codecov without a proper CODECOV_TOKEN. See PR desc for more.

> Coverage report for Python code
> -------------------------------
>
>                 Key: BEAM-2762
>                 URL: https://issues.apache.org/jira/browse/BEAM-2762
>             Project: Beam
>          Issue Type: Task
>          Components: sdk-py-core, testing
>            Reporter: Mark Liu
>            Priority: P2
>              Labels: beam-fixit
>             Fix For: Not applicable
>
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> It's good to have code coverage in Python SDK to show the test coverage. Java is using jacoco-maven-plugin to generate coverage report and coveralls service to manage/display data. 
> Python have similar tool called coverage.py for report generation and coveralls-python to send report to api of coveralls service. 
> It's nice to have one place (like coveralls service) to manage and show data from different SDKs together/separately. However, there are still some problems due to the fact of Beam CI system and multi languages in Beam. The coveralls service doesn't have a good way to collect data separately from different projects. But the postcommit builds are separated by sdks. 
> As the first step, I think it's good to have the python coverage report printout in the build to give people a idea of the current coverage status at lease.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)