If the last record in the Command Log is a canceled or aborted XHR the test shows failure

[bahmutov]

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

git checkout problem
npm install
npm run local

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

[jennifer-shehane]

Could you provide a reproducible example please? 😄

[bahmutov]

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

Hi all,
I have a test for a react app for a login page. On that page there is a request fired to get an access token which is supposed to fail with a 401 which it does. So I'm trying to visit a page (in a logged out state) which is supposed to give me a 401, but I'm ignoring it with {failOnStatusCode: false}, however it displays that the test fails (see screenshot above).
What am I doing wrong?
Interestingly enough, when I run the same test 'headless' it tells me it's passing. Is there a bug in the visualization?

[panzarino]

I think that this could be a regression introduced by some of the changes that I made for studio - I'll investigate

[panzarino]

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 6.4.0.

[cypress-bot]

The code for this is done in cypress-io/cypress#15037, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

[cypress-bot]

Released in 6.5.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v6.5.0, please open a new issue.