Anyway, this looks like a valuable contribution, and it's always good to see more well-supported tools in the Node ecosystem.
What I am wondering is why a new code coverage module was built, yet wasn't made available as a separate module. Is it really that dependent upon this particular testing framework?
The title might be a bit misleading, but a first commit to Whiskey was actually made about a year ago (https://github.com/cloudkick/whiskey/commits/master?page=12), before Mocha existed.
Also there's http://vowsjs.org/
This is a nice achievement but I think if you extracted the process orchestration part and made it use mocha for test layout, running of individual test files, and reporting (which it does a really good job at) it would be more useful.
npm test
So if you open the package.json (https://github.com/cloudkick/whiskey/blob/master/package.jso...) you'll see that `test` runs `make test`.
Check out the Makefile (https://github.com/cloudkick/whiskey/blob/master/Makefile) to see what `npm test` is doing. This abstracts out the test command, because you could be running `cake test`, `make test`, `node whiskey test`, etc. and if you're just using the node package, you probably don't care what the command is, you just want to run the tests. `npm test` is the way to do it.