-
-
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
Need functionality to stop test suite when a test is failing #10129
Comments
Isn't this |
No bail doesn’t run next test suite
fre 5 juni 2020 kl. 09:33 skrev Simen Bekkhus <notifications@github.com>:
… Isn't this --bail?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#10129 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AG7INMHVG6ICAMZDEXUEEUTRVCNVDANCNFSM4NTJJ4IA>
.
|
https://jestjs.io/docs/en/24.x/configuration#bail-number--boolean why it doesn't work? |
The bail option is working only for test suites (aka |
This |
Any update on this without having to use the Jasmine fail fast hack? |
This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue was closed because it has been stalled for 7 days with no activity. Please open a new issue if the issue is still relevant, linking to this one. |
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. |
We need a way to stop a Jest test suite after first failing test. Our test suites are flows and test are steps dependent on the previous step. I know that this is not best practices for unit testing but our use case is different.
We are using Jest Circus so we are getting events about all test in our customized Jest environment class. We want a method to trigger stop of the test suite and mark the remain test as skiped or failed.
Motivation
This is the only missing functionality we are missing in Jest to run our end 2 end test suites.
The text was updated successfully, but these errors were encountered: