This release fixes a class of tests which report as false positives. Certain tests will now break, though they would have previously been reported as passing. Details below. Sorry for the inconvenience!

:bug: Fixes

#3226: Do not swallow errors that are thrown asynchronously from passing tests (@boneskull). Example:

```js it('should actually fail, sorry!', function (done) { // passing assertion assert(true === true);

// test complete & is marked as passing done();

// ...but something evil lurks within setTimeout(() => { throw new Error('chaos!'); }, 100); }); ```

Previously to this version, Mocha would have silently swallowed the chaos! exception, and you wouldn't know. Well, now you know. Mocha cannot recover from this gracefully, so it will exit with a nonzero code.

Maintainers of external reporters: If a test of this class is encountered, the Runner instance will emit the end event twice; you may need to change your reporter to use runner.once('end') intead of runner.on('end').
#3093: Fix stack trace reformatting problem (@outsideris)

:nut_and_bolt: Other

#3248: Update browser-stdout to v1.3.1 (@honzajavorek)

5.0.1

Diff

boneskull

published 5.0.1 • 7 years ago

Changelog

Source

5.0.1 / 2018-02-07

...your garden-variety patch release.

Special thanks to Wallaby.js for their continued support! :heart:

:bug: Fixes

#1838: --delay now works with .only() (@silviom)
#3119: Plug memory leak present in v8 (@boneskull)

:book: Documentation

#3132, #3098: Update --glob docs (@outsideris)
#3212: Update Wallaby.js-related docs (@ArtemGovorov)
#3205: Remove outdated cruft (@boneskull)

:nut_and_bolt: Other

#3224: Add proper Wallaby.js config (@ArtemGovorov)
#3230: Update copyright year (@josephlin55555)

5.0.0

Diff

boneskull

published 5.0.0 • 7 years ago

Changelog

Source

5.0.0 / 2018-01-17

Mocha starts off 2018 right by again dropping support for unmaintained rubbish.

Welcome @vkarpov15 to the team!

:boom: Breaking Changes

#3148: Drop support for IE9 and IE10 (@Bamieh) Practically speaking, only code which consumes (through bundling or otherwise) the userland buffer module should be affected. However, Mocha will no longer test against these browsers, nor apply fixes for them.