js-reporters

The Common Reporter Interface (CRI) for JavaScript Testing Frameworks.

| Avoid this: | Do this: | |----------------------------|----------------------------------| | | |

Specification

See Common Reporter Interface for the latest version of the specification.

See also:

• example, illustrates how reporting works in practice.
• frameworks, studies various popular testing frameworks.
• Integrations, a list of real-world implementations.

Help with AsciiDoc (used for the standard document):

• AsciiDoc Syntax Quick Reference
• AsciiDoc User Manual
• AsciiDoc cheatsheet

Background

In 2014, the QUnit team started discussing the possibility of interoperability between JavaScript testing frameworks such as QUnit, Mocha, Jasmine, Intern, Buster, etc. The "Common Reporter Interface" would be an allow integrations for output formats and communication bridges to be shared between frameworks. This would also benefit high-level consumers of these frameworks such as Karma, BrowserStack, SauceLabs, Testling, by having a standard machine-readable interface.

Our mission is to deliver:

• a common JavaScript API, e.g. based on EventEmitter featuring .on() and .off().
• a minimum viable set of events with standardized event names and event data.
• a minimum viable set of concepts behind those events to allow consumers to set expectations (e.g. define what "pass", "fail", "skip", "todo", and "pending" mean).
• work with participating testing frameworks to support the Common Reporter Interface.

Would you be interested in discussing this with us further? Please join in!

• Join the Chat room
• Browse open issues
• Help frameworks and runners implement the spec

js-reporters Package

Usage

Listen to the events and receive the emitted data:

// Use automatic discovery of the framework adapter.
const runner = JsReporters.autoRegister();

// Listen to standard events, from any testing framework.
runner.on('testEnd', (test) => {
  console.log('Test %s has errors:', test.fullName.join(' '), test.errors);
});

runner.on('runEnd', (run) => {
  const counts = run.testCounts;

  console.log('Testsuite status: %s', run.status);
  console.log('Total %d tests: %d passed, %d failed, %d skipped',
    counts.total,
    counts.passed,
    counts.failed,
    counts.skipped
  );
  console.log('Total duration: %d', run.runtime);
});

// Or use one of the built-in reporters.
JsReporters.TapReporter.init(runner);

Runtime support

• Internet Explorer 9+
• Edge 15+ (Legacy)
• Edge 80+ (Chromium-based)
• Safari 9+
• Firefox 45+
• Chrome 58+
• Node.js 10+

Adapter support

| Testing framework | Supported | Last checked | Unresolved |--|--|--|-- | QUnit | 1.20+ | ✅ [email protected] (Apr 2021) | – | Jasmine | 2.1+ | ✅ [email protected] (Apr 2021) | – | Mocha | 1.18+ | ✅ [email protected] (Apr 2021) | –

See also past issues.

API

autoRegister()

Automatically detects which testing framework you use and attaches any adapters as needed, and returns a compatible runner object. If no framework is found, it will throw an Error.

JsReporters.autoRegister();

Integrations

Runners:

• QUnit, natively since QUnit 2.2.
• Jasmine, via js-reporters JasmineAdapter.
• Mocha, via js-reporters MochaAdapter.

Reporters:

• TAP, implements the Test Anything Protocol for command-line output.
• browserstack-runner, runs JavaScript unit tests remotely in multiple browsers, summarize the results by browser, and fail or pass the continuous integration build accordingly.
• Add your own, and let us know!

Cross-project coordination

Testing frameworks:

• QUnit issue (Done!)
• Mocha issue (pending…)
• Jasmine issue (pending…)
• Intern issue (pending…)
• Vows issue (pending…)
• Buster issue (Discontinued.)
• Nodeunit issue (Discontinued.)

Reporters and proxy layers:

• BrowserStack (Done!)
• Karma (pending…)
• grunt-saucelabs (pending…)
• Testling (pending…)

Credits