You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2022/01/11 16:58:03 UTC

[jira] [Commented] (BEAM-12645) Report Go Code Coverage

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

Beam JIRA Bot commented on BEAM-12645:
--------------------------------------

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.

> Report Go Code Coverage
> -----------------------
>
>                 Key: BEAM-12645
>                 URL: https://issues.apache.org/jira/browse/BEAM-12645
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-go, testing
>            Reporter: Robert Burke
>            Assignee: Miguel Anzo
>            Priority: P3
>              Labels: stale-assigned
>          Time Spent: 4h 10m
>  Remaining Estimate: 0h
>
> It might be nice to have Go test code coverage reported for PRs that affect the Go SDK.
> The go tool reports package level coverage numbers with the -cover flag.
> From sdks/go/pkg/beam one can run `go test -cover ./...`  to get each package's coverage numbers.
> A blog post about that flag, and the related stand alone tool, including getting coverage profiles:
> [https://blog.golang.org/cover
> ]
> It can integrate with the existing python codecov tool as described here:
> https://about.codecov.io/blog/getting-started-with-code-coverage-for-golang/



--
This message was sent by Atlassian Jira
(v8.20.1#820001)