…m/cloudhead/vows/issues#issue/16): Sometimes you want to test an object that inherits from EventEmitter. In this case, if you return said testable object as the topic, then the code hangs if the EventEmitter subclass instance that I'm testing doesn't emit "success" or "error."
This makes it possible to skip the calls to `addBatch` by using optional parameters inside the `describe` method. This is a small change that allows the developer to focus on the code of the tests, thinking of it think of them in terms of data structure instead of Vows' API. The less that the Vows API is present in a test case, the less distracting it is. With this, you could choose to focus solely on the structure of the test and ignore Vows is present by importing only `describe`. This is an entirely backwards compatible change that does not effect any other code. It is fully tested inside the existing tests.
Other than the "works on my system" setup, not sure the best way to go about testing this. Compiling it and running it on my system works, all vows continue to work. In addition, I've also added typos to the `require('coffee-script')` line to force it to act like CoffeeScript isn't available. It continues to run the `*.js` files and ignores the `*.coffee` files.
…f the tests.