-
Notifications
You must be signed in to change notification settings - Fork 528
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 coveralls for code coverage #351
Conversation
@benthemonkey thanks for this but could we open up issues before starting these types of PR please. Gives everyone a chance to discuss it or give any info on other plans we may have had. I'll leave this one for @Snugug |
OK will do next time. |
I just looked over the language I used in this PR. I updated it to not be as assuming, given that I didn't ask permission before submitting this PR. 😄 |
12dddcf
to
a863250
Compare
We're busy! I'm OK merging this in as long as you update to the latest We can debate the merits of code coverage elsewhere |
a863250
to
da1d43b
Compare
Done. I'm not trying to be pushy. I know you were away doing exciting things. 😄 |
👅 |
Add coveralls for code coverage
Resolves sasstools#351 outstanding issue
Resolves sasstools#351 outstanding issue
Resolves sasstools#351 outstanding issue
Resolves sasstools#351 outstanding issue
Resolves sasstools#351 outstanding issue
Add coveralls for code coverage
Resolves sasstools#351 outstanding issue
Hooray for promoting test coverage!
I submitted this because I was interested in learning about setting up code coverage tools. Also I wanted to know whether the test cases for my rules are covering every branch of the code.
Feel free to close this PR if there are reasons to not include a code coverage tool. If folks are interested in merging this, then @Snugug (or someone with admin access) will have to set up coveralls.io to track this repo.
Additionally, if this gets merged we should add the coveralls badge to the readme.
DCO 1.1 Signed-off-by: Ben Rothman [email protected]