v5.0.2

5.0.2 / 2018-03-05

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!

🐛 Fixes

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

  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)

🔩 Other

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

v5.0.1

5.0.1 / 2018-02-07

...your garden-variety patch release.

Special thanks to Wallaby.js for their continued support! ❤️

🐛 Fixes

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

📖 Documentation

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

🔩 Other

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

v5.0.0

5.0.0 / 2018-01-17

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

Welcome @vkarpov15 to the team!

💥 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.

🎉 Enhancements

• #3181: Add useful new --file command line argument (documentation) (@hswolff)

🐛 Fixes

• #3187: Fix inaccurate test duration reporting (@FND)
• #3202: Fix bad markup in HTML reporter (@DanielRuf)

😎 Developer Experience

• #2352: Ditch GNU Make for nps to manage scripts (@TedYav)

📖 Documentation

• #3137: Add missing --no-timeouts docs (@dfberry)
• #3134: Improve done() callback docs (@maraisr)
• #3135: Fix cross-references (@vkarpov15)
• #3163: Fix tpyos (@tbroadley)
• #3177: Tweak README.md organization (@xxczaki)
• Misc updates (@boneskull)

🔩 Other

• #3118: Move TextMate Integration to its own repo (@Bamieh)
• #3185: Add Node.js v9 to build matrix; remove v7 (@xxczaki)
• #3172: Markdown linting (@boneskull)
• Test & Netlify updates (@Munter, @boneskull)

v4.1.0

4.1.0 / 2017-12-28

This is mainly a "housekeeping" release.

Welcome @Bamieh and @xxczaki to the team!

🐛: Fixes

• #2661: progress reporter now accepts reporter options (@canoztokmak)
• #3142: xit in bdd interface now properly returns its Test object (@Bamieh)
• #3075: Diffs now computed eagerly to avoid misinformation when reported (@abrady0)
• #2745: --help will now help you even if you have a mocha.opts (@Zarel)

🎉 Enhancements

• #2514: The --no-diff flag will completely disable diff output (@CapacitorSet)
• #3058: All "setters" in Mocha's API are now also "getters" if called without arguments (@makepanic)

📖 Documentation

• #3170: Optimization and site speed improvements (@Munter)
• #2987: Moved the old site repo into the main repo under docs/ (@boneskull)
• #2896: Add maintainer guide (@boneskull)
• Various fixes and updates (@xxczaki, @maty21, @leedm777)

🔩 Other

• Test improvements and fixes (@eugenet8k, @ngeor, @38elements, @Gerhut, @ScottFreeCode, @boneskull)
• Refactoring and cruft excision (@38elements, @Bamieh, @finnigantime, @boneskull)

v4.0.1

4.0.1 / 2017-10-05

🐛 Fixes

• #3051: Upgrade Growl to v1.10.3 to fix its peer dep problems (@dpogue)

v4.0.0

4.0.0 / 2017-10-02

You might want to read this before filing a new bug! 😝

💥 Breaking Changes

For more info, please read this article.

Compatibility

• #3016: Drop support for unmaintained versions of Node.js (@boneskull):
  • 0.10.x
  • 0.11.x
  • 0.12.x
  • iojs (any)
  • 5.x.x
• #2979: Drop support for non-ES5-compliant browsers (@boneskull):
  • IE7
  • IE8
  • PhantomJS 1.x
• #2615: Drop Bower support; old versions (3.x, etc.) will remain available (@ScottFreeCode, @boneskull)

Default Behavior

• #2879: By default, Mocha will no longer force the process to exit once all tests complete. This means any test code (or code under test) which would normally prevent node from exiting will do so when run in Mocha. Supply the --exit flag to revert to pre-v4.0.0 behavior (@ScottFreeCode, @boneskull)

Reporter Output

• #2095: Remove stdout: prefix from browser reporter logs (@skeggse)
• #2295: Add separator in "unified diff" output (@olsonpm)
• #2686: Print failure message when --forbid-pending or --forbid-only is specified (@ScottFreeCode)
• #2814: Indent contexts for better readability when reporting failures (@charlierudolph)

👎 Deprecations

• #2493: The --compilers command-line option is now soft-deprecated and will emit a warning on STDERR. Read this for more info and workarounds (@ScottFreeCode, @boneskull)

🎉 Enhancements

• #2628: Allow override of default test suite name in XUnit reporter (@ngeor)

📖 Documentation

• #3020: Link to CLA in README.md and CONTRIBUTING.md (@skeggse)

🔩 Other

• #2890: Speed up build by (re-)consolidating SauceLabs tests (@boneskull)

v3.5.3

3.5.3 / 2017-09-11

🐛 Fixes

• #3003: Fix invalid entities in xUnit reporter first appearing in v3.5.1 (@jkrems)

v3.5.2

3.5.2 / 2017-09-10

🐛 Fixes

• #3001: Fix AMD-related failures first appearing in v3.5.1 (@boneskull)

v3.5.1

3.5.1 / 2017-09-09

📰 News

• 📣 Mocha is now sponsoring PDXNode! If you're in the Portland area, come check out the monthly talks and hack nights!

🐛 Fixes

• #2997: Fix missing xit export for "require" interface (@solodynamo)
• #2957: Fix unicode character handling in XUnit reporter failures (@jkrems)

🔩 Other

• #2986: Add issue and PR templates (@kungapal)
• #2918: Drop bash dependency for glob-related tests (@ScottFreeCode)
• #2922: Improve --compilers coverage (@ScottFreeCode)
• #2981: Fix tpyos and spelling errors (@jsoref)

v3.5.0

v3.5.0 / 2017-07-31

📰 News

• Mocha now has a code of conduct (thanks @kungapal!).
• Old issues and PRs are now being marked "stale" by Probot's "Stale" plugin. If an issue is marked as such, and you would like to see it remain open, simply add a new comment to the ticket or PR.
• WARNING: Support for non-ES5-compliant environments will be dropped starting with version 4.0.0 of Mocha!

🔒 Security Fixes

• #2860: Address CVE-2015-8315 via upgrade of debug (@boneskull)

🎉 Enhancements

• #2696: Add --forbid-only and --forbid-pending flags. Use these in CI or hooks to ensure tests aren't accidentally being skipped! (@charlierudolph)
• #2813: Support Node.js 8's --napi-modules flag (@jupp0r)

🔩 Other

• Various CI-and-test-related fixes and improvements (@boneskull, @dasilvacontin, @PopradiArpad, @Munter, @ScottFreeCode)
• "Officially" support Node.js 8 (@elergy)