How to run coverage test?

[dr-shim]

Is your feature request related to a problem? Please describe.
Nope.

Describe the solution you'd like
Please make a guide or update Makefile to include a coverage test.

Describe alternatives you've considered
Please make a guide or update Makefile to include a coverage test.

Additional context
Nope.

Environment details (if applicable):

• Kubernetes version (e.g. v1.10.2): v1.14
• Cloud-provider/provisioner (e.g. GKE, kops AWS, etc): AWS eks
• cert-manager version (e.g. v0.4.0): v0.15.2
• Install method (e.g. helm or static manifests): helm

/kind feature

[wallrj]

Hello @dr-shim

That's a great suggestion.
If you have time to contribute such a patch I'd be happy to test and review it.
Meanwhile you can get a limited report coverage using the standard go tools. E.g.

go test --coverprofile cover.out ./pkg/util/...
go tool cover  -html=cover.out

There is also some work by @munnerz to extract further coverage data from our E2E tests in #2236, but we still need modify our E2E test scripts to use those coverage enabled binaries and then to publish the coverage report somewhere.
If you'd like to help out with that, please join one of our standup meetings or community meetings to discuss.

/area testing
/priority backlog

[jetstack-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle stale

[jetstack-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle rotten
/remove-lifecycle stale

[jetstack-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/close

[jetstack-bot]

@jetstack-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.