-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: Codecov integration #170
Conversation
Codecov Report
@@ Coverage Diff @@
## master #170 +/- ##
=========================================
Coverage ? 87.64%
=========================================
Files ? 19
Lines ? 963
Branches ? 210
=========================================
Hits ? 844
Misses ? 83
Partials ? 36 Continue to review full report at Codecov.
|
Thanks for initiating that !
Yep, that might be tricky and that's one point I did not mention in #163, it would be good to know where there are holes in the tests before trying to fill them more or less blindly. |
This is great. I was going to add Codecov myself at some point as the coverage is being built up, as so far the only indicator has been the output of |
I just realised that Travis is not using |
I have a ugly hack that works for "docker coverage" i.e. I just wanted to know if/how it worked. I'll share the diff here but I can push a branch if needed (or to this branch for further improvement/review).
Now:
|
Nice, I thought it would be more effort than that. The only thing that I'm not quite sure about is replacing Is it sufficient to install |
Sure. As I said, it was a ugly hack just to check it works, I went to the place where I found the string needed to be replaced and just replaced everything.
References: |
Great. No problem with using pytest-cov in the containers - I was just interested what it was doing. |
If you want to turn your work into commits, feel free to add them to this branch. |
Will do |
@takluyver, I did something bad I think, I rebased the branch and forced pushed it. It's in my basic workflow of doing things. When working alone on a branch, it's alright to do so but since you're obviously working on it too, I messed things up in the git history for you... |
Since I already forced push once and then, there were conflict for merging, I rebased and forced push once more. |
I merged the master branch (instead of rebasing) for codecov to process correctly coverage (seems it has trouble with rebasing). We can squash all commits once we're ok with this PR. |
Thanks for following up on this - I didn't have a chance to look at it until now, but happy to see it merged. |
And we're already doing pretty well on coverage, it seems. :-) The biggest chunk of code going unexercised is the function for the |
Try to collect code coverage information & report it through codecov. This is what the results look like: https://codecov.io/gh/pypa/auditwheel/branch/codecov
I think this is only reporting coverage from the unit tests at the moment. I'd like to try to figure out including coverage from the integration tests which run auditwheel inside docker containers, but that will probably be a bit more involved.
I did have to switch to an editable install in Travis. It seems awkward to match up the executed code with the source files otherwise.