-
Notifications
You must be signed in to change notification settings - Fork 57
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
Consider adding code coverage #335
Conversation
Changes Unknown when pulling 2fd6d28 on coverage into * on develop*. |
Okay on core repository only. |
We maybe need to refactore CLI tests in makefile to be executed through Node so we can test CLI coverage? |
That's what I thought, but does not seem to really influence the result ? There is a minor issue: |
|
Changes Unknown when pulling b8073e8 on coverage into * on develop*. |
Changes Unknown when pulling ac24600 on coverage into * on develop*. |
Changes Unknown when pulling 9dcb25e on coverage into * on develop*. |
When is this going to be merged? |
Depends whether we get a consensus from @SassDoc/owners ? I personally like it, it's a good way to motivates us to write more tests, and also discover hidden issues. |
👍 |
👍 |
Changes Unknown when pulling dd76770 on coverage into * on develop*. |
Shall we open an issue about increasing test coverage? 80% is pretty neat, but I'd like us to bump 90-95% if it's doable. |
We won't reach 100% anyway, due to the ES(6|2015) transpilation, there's some snippets from 6to5 that aren't called, and would make no sense for us to test them. |
Just trying out.
Provides some interesting insights on how the codebase is tested.
Travis reports directly to https://coveralls.io
Coveralls add a comment on PRs to report coverage changes. See SassDoc/sass-convert#8
What do you think, useful or not ?