Added optional support for setting global hooks in the browser during setup

[garth]

Example:

mocha.setup('bdd', {
  fail: function(test) { console.log(test); },
  end: function(status) { console.log(status); }
});

mocha.run();

Useful for custom actions on success/failure/completion such as sending status to the server when auto-running a suite in multiple browsers

[tj]

i'd rather just expose the runner so you can listen on any event without any duplicate effort

[garth]

Yes, I thought about that too, but I also wanted pass along the Base.stats to the end function, but then you'd have to expose some more ugly bits too and end up with more complex api.

Any suggestions?

[garth]

Of course this commit will work for any event on the runner.

[tj]

IMO mocha.run() should return the Runner, and should be passed the the reporter, defaulting to HTML like it is right now, so you would do:

var reporter = new mocha.reporters.HTML;
var runner = mocha.run(reporter);

runner.on('whatever', dosomerthingwithreporter);

[tj]

mocha.run() now returns the runner