-
Notifications
You must be signed in to change notification settings - Fork 3.3k
cy.intercept is shown as processing #14655
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
Comments
Hmm yeah, all requests are cleared once the test ends, so there is no longer a reference to the log to end it... Most likely the best fix is to update all unresolved request logs before each test to note that they were incomplete. |
Yup
…Sent from my iPhone
On Jan 22, 2021, at 13:33, Zach Bloomquist ***@***.***> wrote:
Hmm yeah, all requests are cleared once the test ends, so there is no longer a reference to the log to end it...
Most likely the best fix is to update all unresolved request logs before each test to note that they were incomplete.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
The code for this is done in cypress-io/cypress#16730, 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.3.0
In this two test scenario
I have noticed that the last XHR of the first test never completes
never-completes.mp4
Reproduction
Repo and branch https://github.com/cypress-io/cypress-example-recipes/tree/runaway-test
cd examples/stubbing-spying__intercept
npm run dev
spec.js
Note that if there is no second test, or if the first test is
it.only
then everything is fine, the XHR completes right away. So something about the state is leaking from one test into another I guessThe text was updated successfully, but these errors were encountered: