added scoverage and coveralls support #71
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rpless
changed the title
|
Changes Unknown when pulling 3ab4e28 on rpless:coveralls into * on finagle:master*. |
|
This is amazing Ryan @rpless! Thanks a lot! Looks like everything is ready for the 0.1.6 release. |
vkostyukov
added a commit
that referenced
this pull request
Aug 19, 2014
added scoverage and coveralls support
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've added scoverage to the build which can be used locally by running
sbt clean scoverage:test. Right now its bare bones. It will just generate a report and because of a bug will not even do highlighting in reports.I've also added coveralls support to get actual highlighted reports. You can see an example coverage report from my branch at https://coveralls.io/builds/1100597.
Whenever a travis-ci build runs, a coverage report will automatically be generated.
This is for issue #58.