Closed fuzzmz closed 7 years ago
Hi @fuzzmz
Tests are failing due to a different bug (the test suite generates some random datasets that sometimes don), so don't worry about that right now!
Ill merge this and see if I can get the badge working! Thanks!
As it is now the Travis-CI job won't publish to Coveralls.io because it's under a after_success
step which won't get executed due to the failing tests. I can update this to have it always publish to Coveralls no matter if the build fails or not if you'd like.
Looks like just adding a line to change into the testing directory fixed the issue of correctly calculating the line coverage.
Nice work!
D'oh! Glad you got it working.
On Oct 16, 2017 21:53, "Rob Schaefer" notifications@github.com wrote:
Looks like just adding a line to change into the testing directory https://github.com/schae234/Camoco/blob/3adc6203254e417965c1add532be95c1e9edd4c7/.travis.yml#L40 fixed the issue of correctly calculating the line coverage.
Nice work!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/schae234/Camoco/pull/72#issuecomment-336994157, or mute the thread https://github.com/notifications/unsubscribe-auth/ABRfjRtZKg35jf45gYOuXo3f_zyiudcNks5ss6YNgaJpZM4P659v .
This should be the only change required in the build config in order to publish the coverage report to Coveralls.io. Other than this you should just go to coveralls.io and enable code coverage for this repo.
Tried to test it, but Travis-CI builds were failing for me, so I added an
after_failure
step with coveralls publishing just to see if the API works, and it seems to be ok (see here).I say seems to be ok because it gives 0% coverage, but I'm not sure that's because of the failing tests or not. Any idea on this, or on how to better test it?
Fixes #72