[
https://issues.apache.org/jira/browse/BEAM-12645?focusedWorklogId=731293&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-731293
]
ASF GitHub Bot logged work on BEAM-12645:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 23/Feb/22 00:47
Start Date: 23/Feb/22 00:47
Worklog Time Spent: 10m
Work Description: lostluck commented on pull request #16925:
URL: https://github.com/apache/beam/pull/16925#issuecomment-1048350867
R: @aaltay
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 731293)
Time Spent: 4.5h (was: 4h 20m)
> 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
> Fix For: Missing
>
> Time Spent: 4.5h
> 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)
