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 2021/09/20 17:24:01 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=17417747#comment-17417747 ]
Beam JIRA Bot commented on BEAM-12645:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.
> 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
> Priority: P2
> Labels: stale-P2
>
> 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.3.4#803005)