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
When running any test suite in a pipeline I always make sure to give the --forbid-only flag. When doing that with this package it exits the process with a non-zero exit code.
In fact, when I have 10 tests, it will fail with exit code 10. When I have 9 it will exit with 9 etc.
Are you using .only internally to make the parallelism work? If you do the implementation of --forbid-only can't be simply passed to Mocha. If not, this is probably a bug.
When running any test suite in a pipeline I always make sure to give the
--forbid-only
flag. When doing that with this package it exits the process with a non-zero exit code.In fact, when I have 10 tests, it will fail with exit code 10. When I have 9 it will exit with 9 etc.
Are you using
.only
internally to make the parallelism work? If you do the implementation of--forbid-only
can't be simply passed to Mocha. If not, this is probably a bug.To make this work as expected we'll probably have to add some logic to https://github.com/mocha-parallel/mocha-parallel-tests/blob/master/src/bin/options/forbid-only.ts.
For now, I'll work around this with a linting rule to make sure no test is set to
.only
. https://github.com/lo1tuma/eslint-plugin-mocha/blob/master/docs/rules/no-exclusive-tests.mdThe text was updated successfully, but these errors were encountered: