I find it a little strange that this post mentions Expresso but not its successor Mocha, which appears to have been started about the same time as Whiskey.
Anyway, this looks like a valuable contribution, and it's always good to see more well-supported tools in the Node ecosystem.
I currently use mocha with the Jasmine-like interface, and I don't believe I will change.
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?
Disclaimer: I'm author of the blog post.
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.
I'm somewhat new to Node, but why do they have you run the test suite like this:
npm test
A little bit OT, but did anyone else find that the fixed header on the blog made the article less pleasant to read? I kept trying to get it off the screen to focus on the article, and it felt like it was "covering up" something I wanted to see.