Code coverage

[manmartgarc]

Pre-submission Checklist

• I have verified this would not be more appropriate as a feature request in a specific repository
• I have searched existing discussions to avoid duplicates

Your Idea

Hey folks,

Wanted to get a feel on how contributors feel about publishing code coverage metrics like the rust-sdk package.

We can go from something very simple like something that parses go test -v ./... -coverprofile=coverage.out and manually generate a badge, although this requires the workflow to commit back the change, to something more robust like using codecov or coveralls.

I would like to contribute to this feature but wanted to hear from other folks first if there's any reason why it hasn't been done yet.

Scope

• Protocol Specification
• SDK Features
• Documentation
• Developer Experience
• Other

[jba]

I would support using codecov, as is done here.

I'm a little skeptical of driving our testing to push the number up, but we can try it out.

[manmartgarc]

Sounds good. I think the only ask from maintainers would be to set up a codecov token in the repo secrets so we can refer to it via GH actions.

Totally agree with being skeptical of chasing a higher coverage for its own sake; I was thinking of it more as a signal to users. As you say, it can be removed if it spawns a bunch of coverage driven development :)