-
-
Notifications
You must be signed in to change notification settings - Fork 149
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
Error: Unexpected state in afterSpecHandler when chrome browser crashes #1172
Comments
Hi @AMEntwistle, I've fixed this with v20.0.3 |
Fantastic, thank you @badeball |
This probleme (or similare) was anew present, you can see the thread here : https://stackoverflow.com/questions/78687721/unexpected-state-in-beforespechandler-uninitialized-while-running-feature-file/ |
@Rachel-BAO, if you're trying to solicit help, then you need to follow contributing guidelines. This almost always entails providing a reproducible example. |
Current Behaviour
When the chrome browser crashes during test execution, an error is thrown and the plugin does not exit gracefully:
Desired Behaviour
It would be great if the plugin would handle this error. Currently this throws cypress into an exit which means other plugins depending that run after this may not run. In our instance this actually leads to false positives. Chrome memory errors have been an issue with cypress for some time now so being able to handle this scenario would be beneficial.
Test code to reproduce
-->
Versions
The text was updated successfully, but these errors were encountered: