The `promises-es6-tests` package provides a compliance test suite specifically designed for the **draft** ECMA-262 6th Edition (ES6, now ES2015) Promises specification. Released at version 0.5.0, it explicitly states that it should not be considered final or complete and does not supersede the Promises/A+ test suite, advising users to run both. The package enables testing of Promise implementations in both Node.js and browser environments by requiring a minimal adapter interface, an extension of the Promises/A+ adapter. Due to its focus on a draft specification that was finalized as ES2015 in June 2015, and its last release being version 0.5.0, this package is effectively outdated and provides checks against an early, non-final version of the standard rather than the stable ES2015 Promises. Its utility for modern Promise implementations is therefore very limited, as the specification it targets has evolved significantly.
npm install promises-es6-testsVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates how to programmatically run the `promises-es6-tests` suite against a minimal adapter for a native Promise implementation in Node.js, reporting the number of test failures.
For current ECMAScript Promise compliance, refer to official test262 project or more recent testing libraries.
Ensure your test runner executes both `promises-aplus-tests` and `promises-es6-tests` (if targeting the specific ES6 draft features).
Consider newer, actively maintained test suites for modern Promise compliance, or integrate directly with the official test262 project.
Carefully implement the `defineGlobalPromise` and `removeGlobalPromise` methods in your adapter to correctly set up and tear down the `Promise` implementation under test within the provided `globalScope`.
Install the package globally: `npm install -g promises-es6-tests` or run it from a local `node_modules/.bin` via `npm test` script: `"test": "promises-es6-tests test_adapter.js"`.
Ensure your adapter object implements all required methods as specified in the README, including `defineGlobalPromise(globalScope)` and `removeGlobalPromise(globalScope)`.
Verify that the `Promise` constructor made available to the tests via your adapter's `defineGlobalPromise` is a proper, spec-compliant Promise constructor.
No dependency data recorded yet.