0.5.6

Steal-tools's process shim was overriding the process shim that testee-client should have, and as a result, steal was failing a test where the result of process.cwd() was an empty string (due to steal-tools's process shim) instead of "/" (testee-client's process shim). The dist files were rebuilt without steal-tool's process shim, resolving this conflict.

c36b3cf

Don't ignore dist

To avoid breaking CI builds, dist folder isn't ignored.

#50

Fix tests and CI build

• Upgrade QUnit@2
• Fix using core-js/client usage to global instead of amd
• Fix QUnit@1 tests

#49

Better error handling in Mocha

When hooks fail in Mocha, regular failure messages are sent back to the testee runner, but currently the testee reporting server only understands failure on individual tests, not hooks run outside of them.

With this release, if a before/beforeEach/afterEach/after hook fails, the most contextually relevant test is updated with the hook failure on the reporter side.

In addition, a failure on the server side to accept a patch to a nonexistent test was causing an infinite loop of promise rejections in Chrome. This has also been fixed.

DEPRECATED RELEASE

Use v0.5.3 or later. v0.5.2 was released without a dist/ folder, which breaks the testee runner.

QUnit 2 support

The patch release official declares testee-client support for QUnit 2. While the changes in this release do not actually change anyone's code as testee-client had already supported QUnit 2, we now do have test coverage around QUnit 2 solidifying that feature.