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

["Kenneth Knowles (Jira)" <ji...@apache.org>]

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

Kenneth Knowles updated BEAM-2762:
----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Resolved)

Hello! Due to a bug in our Jira configuration, this issue had status:Resolved but resolution:Unresolved.

I am bulk editing these issues to have resolution:Fixed

If a different resolution is appropriate, please change it. To do this, click the "Resolve" button (you can do this even for closed issues) and set the Resolution field to the right value.

> 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, stale-P2
>             Fix For: Not applicable
>
>          Time Spent: 3h 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)