Closed mboersma closed 8 years ago
AFAICT, this is actually working correctly, but codecov.io has no baseline coverage report against which to compare these results. Chicken-and-egg thing.
I noticed that if there are no tests in a given go package, it doesn't get included. I think we would prefer for it to show "0% coverage," which might be accomplished by fabricating an entry in coverage.txt
.
I'm curious if anyone who has worked with codecov.io has input on this. I'd like to sort it out and do something similar for all Deis Workflow go packages.
No coverage report found for master at 43a66c9.
Powered by Codecov. Last updated by 43a66c9...4589558
@mboersma I restarted the e2e build. hopefully it passes 😄
Summary of Changes
make test-cover
runs the go unit tests while accumulating acoverage.txt
file suitable for shipping to https://codecov.io/. This also adds a badge to README.md:TODO:
Issue(s) that this PR Requires
deis/docker-go-dev#34
Testing Instructions
Please provide a detailed list for how to test the changes in this PR.
Build a localdeis/go-dev:latest
image from the PR referenced abovemake test-cover
Anticipated results:
coverage.txt
file present containing code analysis dataNext steps:
Help me figure out how to uploadcoverage.txt
to codecov.ioPull Request Hygiene TODOs
Please make sure the below checklist is complete.