-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Move coverage script to Makefile #503
Conversation
Also includes some cleanup of unnecessary files in .gitignore which should belong in a global .gitignore.
Awesome! 👍 |
|
||
lib-coverage/ | ||
sass-coverage.js | ||
**/fixtures/**/build.* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This shouldn't be needed either. If that's needed it means that tests are failing/are badly written.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh yes! (unlink!!) I think it was due to the faulty libsass code during the testing. :)
Changes Unknown when pulling 17e11ae on kevva:coverage into * on sass:master*. |
Perfect! Coverage 95%! 👍 @andrew, LGTM! |
It's only testing the API though, not the CLI. We can't run the |
@kevva Can you re-add |
@andrew, there's |
Ah, good spot, code review on mobile is tricky! |
Move coverage script to Makefile
LOL! That's true. Most honest mistakes transpire due to mobile technology. |
👎 Makefiles don't work on Windows, this is why we had the NPM and node scripts |
This is only for the coverage stuff which is used by Travis anyway. That's why I kept Another solution is to move the whole test suite to gulp or something. Anything that's more reliable and pretty than writing shell scripts using shelljs. |
The coverage can also be setup on Windows with AppVeyor, but not if we use a Makefile. |
No problem. I'm kinda agreeing with you. It's not ideal to have both those scripts and a Makefile. But we should aim to replace those scripts with something better. The |
Yeah, I didn't do Grunt/Gulp before because there was no pressing need at the time. Now that there are more people working, it might be good for that to be revisited. |
I'm still not a fan of grunt/gulp, npm scripts solves things in a simple way. I completely forgot about makefiles on windows too 😦 |
👍 for using npm scripts over grunt (http://blog.keithcirkel.co.uk/why-we-should-stop-using-grunt/) |
+1 for using anything over grunt. That article got so many facts wrong about gulp though and shouldn't be treated as an argument for stop using it (not saying we should use gulp here though). |
Fixes build to report correctly to coveralls.io
Also includes some cleanup of unnecessary files in .gitignore which should belong
in a global .gitignore.