This repository has been archived by the owner. It is now read-only.

Use coveralls.io to display testing coverage? #761

Closed
ollieparanoid opened this Issue Oct 13, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@ollieparanoid
Member

ollieparanoid commented Oct 13, 2017

PR #760 will integrate automatic testing on Travis CI, at least for the fast testcases. I would like to display how much testing coverage we have for pmbootstrap in the README.md (with a badge and with details when you click on it).

Proprietary service coveralls.io looks like a nice interface and is free to use for open source projects. It is compatible to GitHub and gitlab in case we decide to move there.

I have not found a similar service, where the source code is available (is there any?).

Worst case is, that for some reason we suddenly can't use that service anymore and lose the coverage reports from the past. We can always generate coverage reports ourselves with pytest-cov (which is the output that gets used for coveralls.)

And of course the upside is, that this motivates (at least me) to make more testcases and have good testing coverage.

So what do you think about this proposal, fellow hackers?

@MartijnBraam

This comment has been minimized.

Show comment
Hide comment
@MartijnBraam

MartijnBraam Oct 13, 2017

Member

coveralls is pretty nice, you can even configure it to make it deny a PR when the coverage drops too much if it gets merged.

I also haven't found any nice open solutions yet, gitlab has some very very sloppy coverage integration (it parses the coverage percentage from your gitlab-ci log and then basically thows away that information).

Member

MartijnBraam commented Oct 13, 2017

coveralls is pretty nice, you can even configure it to make it deny a PR when the coverage drops too much if it gets merged.

I also haven't found any nice open solutions yet, gitlab has some very very sloppy coverage integration (it parses the coverage percentage from your gitlab-ci log and then basically thows away that information).

@PabloCastellano

This comment has been minimized.

Show comment
Hide comment
@PabloCastellano

PabloCastellano Oct 19, 2017

Member

Go for it. The trade-off looks good to me and we can always implement another coverage tool that comes out and we like more.

Member

PabloCastellano commented Oct 19, 2017

Go for it. The trade-off looks good to me and we can always implement another coverage tool that comes out and we like more.

PureTryOut added a commit that referenced this issue Feb 21, 2018

Close #761: Integrate coveralls.io to show test coverage (#820)
* Enable coveralls.io coverage reports
* Add badge to README.md
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.