You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 7, 2018. It is now read-only.
We on the QUnit team have been discussing the possibility of working with other JS test frameworks that can be run client-side (e.g. Mocha, Jasmine, Intern, etc.) to agree upon a standard Reporter interface so that we could hopefully share Reporter plugins between testing frameworks.
This would most likely come in the form of an EventEmitter interface (.on(...)/.off(...)) with an agreed upon:
minimum viable set of standardly-named events
associated standard set of data/details provided for each event
minimum viable set of standard test status types (e.g. pass, fail, skip, todo, pending, etc.)
Would you guys be interested in discussing this further with us?
We on the QUnit team have been discussing the possibility of working with other JS test frameworks that can be run client-side (e.g. Mocha, Jasmine, Intern, etc.) to agree upon a standard Reporter interface so that we could hopefully share Reporter plugins between testing frameworks.
This would most likely come in the form of an EventEmitter interface (
.on(...)
/.off(...)
) with an agreed upon:Would you guys be interested in discussing this further with us?
If so, I've added @cjohansen, @augustl, and @dwittner to a "Team Buster" group for https://github.com/js-reporters/js-reporters.
Discussions: https://github.com/js-reporters/js-reporters/issues/
Cross-reference issues:
The text was updated successfully, but these errors were encountered: