I fought with this for a while and it wasn't as straightforward as I thought it would be. The root issue is that I'm trying to check all these boxes before it will work properly:
[ ] uses Coveralls (not aware of another reporting service that supports node and integrates with Travis)
[ ] can report on CoffeeScript (most are built for JavaScript)
[ ] ties into the Grunt command (we default to using grunt test, so we would want grunt coverage)
[ ] executes alongside Travis CI run (branch builds already run tests)
The objective with code coverage is to a) monitor the test coverage differences with new features added and b) advertise that this package has decent test coverage.
I may come back to this, but anyone who wants to take a swing at it is more than welcome.
I fought with this for a while and it wasn't as straightforward as I thought it would be. The root issue is that I'm trying to check all these boxes before it will work properly:
grunt test, so we would wantgrunt coverage)The objective with code coverage is to a) monitor the test coverage differences with new features added and b) advertise that this package has decent test coverage.
I may come back to this, but anyone who wants to take a swing at it is more than welcome.