-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--bail
does not work
#2626
Comments
Running Jest with @cpojer I think we should stress this better in the documentation, right? |
Oh, I see, thanks for the info :) |
I have jest v 18.1.0 and have |
This should be fixed in master, we fixed yet another issue with bail. |
Actually, I just realized that this was because a script in my "setupFiles" had an error. It looks like if a test suite fails to run, that doesn't trigger the "bail" and it moves on to the next suite (which will re-run the "setupFiles" scripts and fail for the same reason...) |
is there any way to skip current describe and all nested describe on first failure but still run other describes? Like |
According to documentation https://jestjs.io/docs/en/api#describename-fn, a describe is a test suite. But --bail is not really working when first test suite fails. |
I've made some temporary kludge for it: https://stackoverflow.com/a/53615538/2051938 |
I'm hitting the same issue. Also, should coverage still be running on a bail? I'd think it'd just halt everything |
Maybe, for clarity, we can rename |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Do you want to request a feature or report a bug?
bug
What is the current behavior?
All tests are run even though
--bail
was used.What is the expected behavior?
No other tests should be run after an error.
See https://github.com/julien-f/issue-jest-bail
Environment
My system is Debian Stretch.
The text was updated successfully, but these errors were encountered: