[
https://issues.apache.org/jira/browse/BEAM-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17154170#comment-17154170
]
Beam JIRA Bot commented on BEAM-2762:
-------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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: Saavan Nanavati
> Priority: P2
> Labels: beam-fixit, stale-assigned
> Fix For: Not applicable
>
>
> 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)
