A retrospective of how Astro migrated more than 500 test suites from Mocha to Node.js test runner.
9.0.0 / 2021-06-07 ð¥ Breaking Changes #4633: Drop Node.js v10.x support (@juergba) #4635: import-first loading of test files (@giltayar) Mocha is going ESM-first! This means that it will now use ESM import(test_file) to load the test files, instead of the CommonJS require(test_file). This is not a problem, as import can also load most files that require does. In the rare cases where this fails, i
8.0.0 / 2020-06-10 In this major release, Mocha adds the ability to run tests in parallel. Better late than never! Please note the breaking changes detailed below. Let's welcome @giltayar and @nicojs to the maintenance team! ð¥ Breaking Changes #4164: Mocha v8.0.0 now requires Node.js v10.12.0 or newer. Mocha no longer supports the Node.js v8.x line ("Carbon"), which entered End-of-Life at the end
Prerequisites Checked that your issue isn't already filed by cross referencing issues with the common mistake label Checked next-gen ES issues and syntax problems by using the same environment and/or transpiler configuration without Mocha to ensure it isn't just a feature that actually isn't supported in the environment in question or a bug in your code. 'Smoke tested' the code to be tested by run
Addresses #2352 Updated version of #3194 Commit has correct Git credentials this time and Travis / Appveyor configs are now properly updated. Description of the Change Where possible, I tried to exactly duplicate the design of the Makefile using nps. I've tested it by running build and test commands, as well as granular testing of individual commands against a vanilla repo to ensure it's running t
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 f
Top modern browsers already support ES6 modules. This is great news from the unit testing perspective. A browser can natively load and test project sources without transpiler. As a developer I would love to utilize this feature! Removing extra steps from the development process will improve speed and productivity. Below is a story of how I got it working with Mocha test-runner.
Mocha v4.0.0 is nearing release. With this new version also comes the obligatory breaking changes, and I'll enumerate them below. UPDATE (April 18, 2018): Mocha v4 was released on October 2, 2017. Mocha Will No Longer Support Node.js Pre-v4.0.0 There are several reasons for this: These versions of Node.js are no longer maintained and (some) have known security vulnerabilities which will not receiv
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.) wi
At Automattic we use Mocha to run all tests written for Calypso project which powers WordPress.com. It also includes end-to-end tests, which live in their own repository. We have been using this setup for over 3 years now. I think it is a good moment to revisit this choice. I found this unit testing tools comparison very helpful when evaluating alternatives. I strongly agree with the conclusions s
ã¡ã³ããã³ã¹
ã©ã³ãã³ã°
ã©ã³ãã³ã°
ãªãªã¼ã¹ãé害æ å ±ãªã©ã®ãµã¼ãã¹ã®ãç¥ãã
ææ°ã®äººæ°ã¨ã³ããªã¼ã®é ä¿¡
å¦çãå®è¡ä¸ã§ã
j次ã®ããã¯ãã¼ã¯
kåã®ããã¯ãã¼ã¯
lãã¨ã§èªã
eã³ã¡ã³ãä¸è¦§ãéã
oãã¼ã¸ãéã
{{#tags}}- {{label}}
{{/tags}}