-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
If the last record in the Command Log is a canceled or aborted XHR the test shows failure #14978
Comments
Could you provide a reproducible example please? 😄 |
Yeah, I will add instructions for reproduction, but want to note that a user also reported same problem here https://gitter.im/cypress-io/cypress?at=6021494e84e66b7f7edd7858
|
I think that this could be a regression introduced by some of the changes that I made for studio - I'll investigate |
I'm saying this before I'm fully certain, but I'm 99% sure that the issue is caused by this and is a regression introduced with the Studio error state updates in |
The code for this is done in cypress-io/cypress#15037, but has yet to be released. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Cypress v6.4.0
Look at the image below: 6 passing tests, no failures, BUT the last test shows the failure icon. I think this happens when the last command in that test is an aborted XHR request
Reproduction
Clone https://github.com/bahmutov/ceceliacreates-nuxt/tree/problem branch
problem
Click on the spec
Notice how this movie shows the status of the test keeps toggling depending on the XHR logs
failing-test-demo.mp4
At the end, the passing test becomes red again after a few more XHRs were cancelled
The text was updated successfully, but these errors were encountered: