You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Pablo Estrada (JIRA)" <ji...@apache.org> on 2017/12/12 00:21: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=16286831#comment-16286831 ] 

Pablo Estrada commented on BEAM-2762:
-------------------------------------

Is this fixed?

> 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
>            Assignee: Mark Liu
>
> 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
(v6.4.14#64029)