diff options
| author | Will LaBranche <[email protected]> | 2014-07-31 16:20:54 -0700 |
|---|---|---|
| committer | Will LaBranche <[email protected]> | 2014-07-31 16:20:54 -0700 |
| commit | 32540bae6ab9122067eb896f6efb4e0a28dc9b07 (patch) | |
| tree | 2d1abb6193a44904bd8d9d88d9da12a94ae9b382 | |
| parent | 4b25348923dc1fb1f304ad2ddae1f73dc1385b65 (diff) | |
| download | node-coveralls-32540bae6ab9122067eb896f6efb4e0a28dc9b07.tar.xz node-coveralls-32540bae6ab9122067eb896f6efb4e0a28dc9b07.zip | |
Removed dead link
Seems to be taken off the blog entirely.
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -45,7 +45,7 @@ NODE_ENV=test YOURPACKAGE_COVERAGE=1 ./node_modules/.bin/mocha \ ``` ### [Mocha](http://visionmedia.github.io/mocha/) + [JSCoverage](https://github.com/fishbar/jscoverage) -Instrumenting your app for coverage is probably harder than it needs to be (read [here](http://www.seejohncode.com/2012/03/13/setting-up-mocha-jscoverage/) or [here](http://tjholowaychuk.com/post/18175682663/mocha-test-coverage)), but that's also a necessary step. +Instrumenting your app for coverage is probably harder than it needs to be (read [here](http://www.seejohncode.com/2012/03/13/setting-up-mocha-jscoverage/)), but that's also a necessary step. In mocha, if you've got your code instrumented for coverage, the command for a travis build would look something like this: ```sh |