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 coveralls for code coverage #351

Merged
merged 1 commit into from
Nov 10, 2015

Conversation

benthemonkey
Copy link
Member

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]

@DanPurdy
Copy link
Member

@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

@benthemonkey
Copy link
Member Author

OK will do next time.

@benthemonkey
Copy link
Member Author

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. 😄

@benthemonkey
Copy link
Member Author

@DanPurdy @Snugug This has been sitting for awhile. I don't mind closing it, but I'd like to hear back about it, when you get the chance.

@Snugug
Copy link
Member

Snugug commented Nov 10, 2015

We're busy!

I'm OK merging this in as long as you update to the latest develop (currently can't be merged).

We can debate the merits of code coverage elsewhere

@benthemonkey
Copy link
Member Author

Done. I'm not trying to be pushy. I know you were away doing exciting things. 😄

@Snugug
Copy link
Member

Snugug commented Nov 10, 2015

👅

Snugug added a commit that referenced this pull request Nov 10, 2015
@Snugug Snugug merged commit f116ade into sasstools:develop Nov 10, 2015
Snugug added a commit to Snugug/sass-lint that referenced this pull request Nov 10, 2015
benthemonkey pushed a commit to benthemonkey/sass-lint that referenced this pull request Nov 12, 2015
benthemonkey pushed a commit to benthemonkey/sass-lint that referenced this pull request Nov 12, 2015
benthemonkey pushed a commit to benthemonkey/sass-lint that referenced this pull request Nov 12, 2015
benthemonkey pushed a commit to benthemonkey/sass-lint that referenced this pull request Nov 12, 2015
donabrams pushed a commit to donabrams/sass-lint that referenced this pull request Nov 19, 2015
donabrams pushed a commit to donabrams/sass-lint that referenced this pull request Nov 19, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants