On https://github.com/devongovett/qunit-cli/blob/master/index.js#L73, it is shown that keeps listening to the 'exit' event after all the tests have passed, just to set the number of failed tests as exit status. Since all the tests have already passed, should it directly call to process.exit()? This way aync tests doesn't get hanging around. Or should I add a new callback on QUnit.done() to call to process.exit()? I find this uglier, since I would need to have different code for Node.js and browser...
On https://github.com/devongovett/qunit-cli/blob/master/index.js#L73, it is shown that keeps listening to the 'exit' event after all the tests have passed, just to set the number of failed tests as exit status. Since all the tests have already passed, should it directly call to process.exit()? This way aync tests doesn't get hanging around. Or should I add a new callback on QUnit.done() to call to process.exit()? I find this uglier, since I would need to have different code for Node.js and browser...