Share a common Reporter interface?

We on the [QUnit](http://qunitjs.com/) team have been [discussing](https://github.com/jquery/qunit/issues/531) the possibility of working with other JS test frameworks, especially those that can be run client-side (e.g. Mocha, Jasmine, Intern, Buster, etc. — and _apparently_ NodeUnit! :astonished:), to agree upon a common Reporter interface so that we could hopefully share Reporter plugins between testing frameworks.

This would most likely come in the form of:
- a common Reporter API/Interface, e.g.
- an EventEmitter interface (`.on(...)`/`.off(...)`) _**OR**_ an object with standard "hook" properties
- _maybe_ a standard-ish way to register a Reporter, e.g. `MyLib.addReporter(x)`, `MyLib.reporter = x;`, etc.
- a minimum viable set of standardly-named events
- an associated standard set of data/details provided for each event
- a minimum viable set of standard test status types (e.g. pass, fail, skip, todo, pending, etc.)
- updating all participating test frameworks to support this new common Reporter interface

Would you guys be interested in discussing this further with us? If so, please let me know who I should invite to participate.

**Centralized Discussions:** https://github.com/js-reporters/js-reporters/issues/

Cross-reference issues:
- https://github.com/jquery/qunit/issues/531 (original discussion)
- https://github.com/visionmedia/mocha/issues/1326
- https://github.com/pivotal/jasmine/issues/659
- https://github.com/theintern/intern/issues/257
- https://github.com/busterjs/buster/issues/419

Commencez par la discussion centralisée sur js-reporters/js-reporters/issues/ et examinez les issues liées de QUnit, Mocha, Jasmine, Intern et Buster. Le payload propose plusieurs conceptions d’interface concurrentes, mais ne mentionne aucun fichier nodeunit, test, responsable de l’implémentation ni critère d’acceptation ; par conséquent, une prochaine étape concrète nécessiterait d’abord un accord sur le périmètre.

Rédigé par le modèle d'indexation à partir du texte de l'issue.