-
Notifications
You must be signed in to change notification settings - Fork 106
code coverage #44
Comments
Currently, no. I am planning on looking into integrating https://github.com/metaskills/mocha-phantomjs instead of our current phantom -> console system, theoretically it would support CI integration. |
For anyone who's interested, I forked this project to add "live" code-coverage enforcement via BlanketJS: Note that this differs from other implementations (such as ones that use Istanbul) which create physical instrumented copies of your source files to check coverage. Blanket does it in-memory. This also allows you to fail the build if a certain minimum coverage threshold is not met. I'm currently using this with TravisCI as shown in one of my projects here: https://travis-ci.org/ModelN/backbone.geppetto/builds/9711973 This also integrates nicely with Jenkins as we're doing on an internal project at my company. |
Is there any movement on this? Is it possible to integrate @geekdave's changes into grunt-mocha proper? |
At this point it's probably better to leave our projects as separate, since they have different goals. I've used my fork on a few projects now, and I've been adding new features frequently, so frankly I'd prefer to stay in control. :) I wrote a blog about it here, if you're interested in learning more: http://www.geekdave.com/2013/08/02/automated-code-coverage-enforcement-for-mocha-using-grunt-and-blanket/ |
Is there a way to tie in code coverage?
Also, I'd like to tie both into jenkins and be able to fail builds if tests fail or if certain amount of lines aren't covered... Any ideas on the best way to do this?
The text was updated successfully, but these errors were encountered: