unable to listen to start event during programmatic run

[grawk]

The 'start' event is emitted synchronously downstream of the mocha.run method. Thus, if you are attaching a listener to that event after calling mocha.run (to get the runner instance), you miss the event:

var runner = mocha.run(function (failures) {
  process.on('exit', function () {
    process.exit(failures);  // exit with non-zero status if there were failures
  });
});
runner.on('start', function (Evt) {
  //never called
});

Maybe there is some other way to attach event listeners to the runner prior to calling run, but I haven't found it yet.

[kunagpal]

This is an issue with Mocha v3.4.2 and should probably be marked as confirmed.

[ScottFreeCode]

I just tried this out to confirm it; looks like we'll want to change

mocha/lib/runner.js

Line 807 in a054380

function start () {

to move the emit and runSuite calls into an asynchronous callback (perhaps Runner.immediately?)... We'll also want a test for it, should be pretty simple -- just new Runner(<whatever the minimum requirement is -- check existing Runner tests>).run().on("start", <spy>).on("end", function() { <assert that spy was called>; done() }), I think.

[boneskull]

linking back to #3065

[fancy967]

Hi guys, any plan to fix this?