Coverage #36
Merged
Coverage #36
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
added 6 commits
March 7, 2015 14:59
|
Changes Unknown when pulling 1a98fee on coverage into * on master*. |
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.
This pull adds pre-commit code coverage tracking. The way it works is a new travis matrix builds with
clang --coverage. Then when the tests are run coverage files are output. Finallycpp-coverallsis used to find those coverage files and upload them to https://coveralls.io/r/osmcode/node-osmium for easy viewing of results.The job runs on OS X because I was unable to get the clang++ on linux to work with the
--coverageflag (some linking errors). Also,node-pre-gypwas upgraded in order to support the--debugflag (key for getting the best coverage reports)./cc @joto