Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add code coverage reporting #42

wants to merge 2 commits into
base: master
Choose a base branch


Copy link

@lightswitch05 lightswitch05 commented Jul 31, 2016

Adds code coverage reporting using Coveralls. This uses the existing code coverage tools, it just adds a final step to Travis CI to report the information to coveralls on success.

To see what the coveralls tool will look like, you can see my fork.

By default, all pull requests are commented on with their code coverage. Here is an example. This behavior can be disabled.

Note: To enable coveralls integration with this original repo, it does require you to log into and allow github integration. The account is free, but I understand if that isn't something you want.

@lightswitch05 lightswitch05 force-pushed the feature/add-code-coverage-reporting branch from b104bf5 to 92caf44 Compare Aug 17, 2016
@lightswitch05 lightswitch05 force-pushed the feature/add-code-coverage-reporting branch from 92caf44 to ccb42c0 Compare Nov 27, 2017
Copy link
Contributor Author

@lightswitch05 lightswitch05 commented Nov 27, 2017

I rebased this pull request with the latest from master. If you merge this pull request and log into Coveralls to allow github integration (free)- then all future pull requests will get a comment saying if the change decreases or increases code coverage. This can be useful to encourage future contributors to write unit tests.

Current code coverage:

Statements   : 100% ( 211/211 )
Branches     : 95.52% ( 64/67 )
Functions    : 100% ( 43/43 )
Lines        : 100% ( 211/211 )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.

None yet

1 participant