You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 running it outside the real test suite to get a better sense of whether the problem is in the code under test, your usage of Mocha, or Mocha itself
Ensured that there is no discrepancy between the locally and globally installed versions of Mocha. You can find them with: node node_modules/.bin/mocha --version(Local) and mocha --version(Global). We recommend avoiding the use of globally installed Mocha.
Description
When using the --bail flag, mocha will exit with a status of 0, instead of 1, when it encounters an error in before hooks. This potentially causes CI to pass when it should fail.
Prerequisites
faq
labelnode node_modules/.bin/mocha --version
(Local) andmocha --version
(Global). We recommend avoiding the use of globally installed Mocha.Description
When using the
--bail
flag, mocha will exit with a status of0
, instead of1
, when it encounters an error inbefore
hooks. This potentially causes CI to pass when it should fail.Steps to Reproduce
Expected behavior: mocha exits with status 1
Actual behavior: mocha exits with status 0
Reproduces how often: 100%
Versions
mocha --version
andnode node_modules/.bin/mocha --version
: not globally installed /5.1.1
node --version
:8.11.1
Ubuntu 16.04.4 LTS x64
bash
Additional Information
None
The text was updated successfully, but these errors were encountered: