Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add support for coveralls.io coverage reports #1539
OK, it's true, those badges in the README might be a little obsession of mine. Nevertheless, it occurs more often than it should that some behaviour in the jekyll code is accidentally broken, yet no test goes
So, while it is not necessary to test every single line and a coverage of 100,000000 % is surely not necessary, some visible report on it can probably help to improve jekyll's (already awesome) testing suite. This PR adds support for coverage analysis during Travis-CI builds and loading them up to coveralls.io (provided @mojombo signs in there with his github account).
See https://coveralls.io/r/maul-esel/jekyll for the current reports of this branch.
OK, it seems CodeClimate test coverage only works if you have a CodeClimate account
As to all the
So, I removed the
However, update on CodeClimate: they're working on support for open-source repos, though it might be some time (reference) and they're also working on the ability to combine coverage results from cucumber and unit tests, which jekyll needs.
I really think that on a long-term basis, using CodeClimate is better because having both their features combined next to each other can surely help a lot. Also, it wouldn't require using another service. So IMO the only question left is if we