Random ordering for mocha
It is very easy to accidentally create a fragile test suite by leaving lingering state after a test case, that is then inadvertently used as a precondition for a subsequent test. This can then cause problems trying to run single tests or test suites in isolation.
By executing files in a random order on each execution of a test suite the risk of accidental introduction of state is eliminated, or at least reduced, since any dependency on leftover state will result in test failures.
Pass choma as a require option to mocha, either by appending to your test command:
> mocha ./tests/ --require choma
or by adding a line to mocha.opts
--require choma
The seed used to generate the random order is output to the console when running your test suite.
If you would like to re-use a seed to re-test a particular execution order, you can set an environment variable of CHOMA_SEED.
> CHOMA_SEED=myseed mocha ./tests/ --require choma
FAQs
Random ordering for mocha
We found that choma demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.