Maybe a bug in 6.0.1 - any ideas?

[Nasicus]

Just upgraded to 6.0.1 and replaced all my cy.route with cy.intercept.

I think this is a bug, but didn't create one yet, since it happens only every ~3 times I run the test and I have no idea why or how to reproduce it.

As you can see it says it timed out waiting for the response, even though it even writes one line above ResponseReceived.

And then I rerun it and sometimes it suddenly works:

Code looks like this:

cy.intercept('POST', '**/b2c_users/with_hash/hash').as('createUser');
// some other test code
// ...
 cy.wait('@createUser');

Note that we have in total around 2400 tests (not all of them use intercept and not all of theme are UI testes, some only test the endpoints). And only this one and another one (same file and same route) fails.

[lpanger]

I'm seeing the same thing and it usually happens with larger and/or slower API calls. Thought maybe there might be a way to intercept only Completed instead of ResponseReceived states but I haven't found anything.

Another maybe unrelated thing is that sometimes this ResponseReceived will have a child and you can expand it in the command log to see Completed.

[Nasicus]

Hmm interesting. So it's not only me.

@jennifer-shehane sorry for mentioning directly.

Should I create a bug out of this? Note that I can still only reproduce it randomly.

[lpanger]

I think this is the bug - #8999. Looks like it's fixed in 6.1.0 but I haven't confirmed

[jennifer-shehane]

Yah, it does look like this bug, if anyone can confirm after upgrading to 6.1.0 this should be fixed.