2.1.2

Upgraded dependencies, notably Mocha, which will ensure Node.js v7 compatibility. (#80, @mgol)

2.1.1

Fixed a bug in the test coverage for 2.2.7, regarding testing the reason values. (#59, #75, @xiaody)

2.1.0

Made the tests browserifiable, by using only static requires

2.0.5

Dependency updates, including to the Mocha test runner.

2.0.4

• Fixed passing no-value Mocha arguments, like --bail, as the last argument to the CLI. (#54, #55 @dtao)
• Reverted the change in 2.0.3, since it didn't actually accomplish anything, except making the code unnecessarily complex. (See discussion in #51.)

2.0.3

• Made the tests for 2.2.5 more tolerant of environments that don't implement strict mode correctly, so that libraries can still be tested accurately in those environments. (#47, @petkaantonov)

2.0.2

• Removed trailing comma that would cause problems on older IE versions. (#46, @petkaantonov)

2.0.1

• Added extra tests to 2.2.1 for ignoring non-callable onFulfilled or onRejected arguments. (#42)
• Fix a typo in 2.3.3 tests for poorly-behaved thenables. (#43, @Steve-OH)

2.0.0

This release brings the test suite up to date with the newly-released version 1.1 of the Promises/A+ specification. Along the way, it vastly increases test coverage, both for new requirements of the 1.1 spec and for existing requirements from the 1.0 spec.

At the same time, we made some updates to the adapter interface, to encourage better practices in promise libraries:

• Adapters now have functions resolved and deferred.resolve, instead of fulfilled and deferred.fulfill. Although we only call these functions with non-thenable values, thus making both "fulfill" and "resolve" correct verbs for these cases, most promise libraries only provide resolve capabilities, and not direct fulfillment capabilities.
• The function to return a { promise, resolve, reject } object is now called deferred instead of pending, keeping with common terminology and practice in promise libraries.