Different intercept behavior in Firefox 151? #33842
-
|
Since last night some of our Cypress tests fail unexpectedly (both in CI and on developer systems). They even fail with older versions of our software; so this is probably not caused by changes in our software. And with Chrome the same tests suceed! We usually run Cypress tests with Firefox. And there was a Firefox upgrade last night (from 150 to Firefox 151). I don't know yet how to install an older FF version in parallel though, so haven't tested with older FF versions. I haven't debugged the problem in detail so far; but it looks like it's related to beforeEach(() => {
cy.intercept({
method: 'GET',
url: /abc
}).as('abcRequest');
...
cy.wait('@abcRequest');
});This Does anyone else see similar problems since the Firefox 151 upgrade? Or do we use Cypress incorrectly here? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
|
Which operating system are you using for your developer and CI systems? Which is your CI provider? You already found #33843 so perhaps Mozilla did something strange with this release? |
Beta Was this translation helpful? Give feedback.
-
|
We have debugged our failing Cypress tests and found a bug in our code: in some of the Cypress tests we accidentally sent two cookies instead of just one. This didn't cause problems before; but I guess with Firefox 151 the two cookies are now sent in a different order, causing different behavior by the backend and leading to the test failure. Thanks for describing changed cookie behavior in #33843; this was helpful when debugging the problem on our side. |
Beta Was this translation helpful? Give feedback.
We have debugged our failing Cypress tests and found a bug in our code: in some of the Cypress tests we accidentally sent two cookies instead of just one. This didn't cause problems before; but I guess with Firefox 151 the two cookies are now sent in a different order, causing different behavior by the backend and leading to the test failure.
Thanks for describing changed cookie behavior in #33843; this was helpful when debugging the problem on our side.