You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Explanation: Clicking on "more-actions" opens a menu. In this menu we click on "remove-site". This menu is supposed to close after an element in the menu was clicked. By clicking "remove-site" a dialog is shown. We close this dialog by clicking the button labeled "Nein". After that we want to open the dialog again and klick the button labelled "Ja".
With Cypress 14 this part of the test failed with an error that said something like "can not click element because it is already detached from dom".
I had to add cy.getBySel('remove-site').should('not.exist'); after the first cy.getBySel('remove-site').click(); to ensure that the second cy.getBySel('remove-site').click(); is not clicking the first element which was still visible. So the tests runs with Cypress 14 now and the code is as follows
After "fixing" the test I compared it running in Cypress 13 and Cypress 14. (the modified test code both in 13 and 14)
The test with Cypress 13
Same test with Cypress 14
Some information: I used cy.wait() for testing proposes and had to wait 5 seconds after cy.getBySel('remove-site').click(); for the menu to disappear and the test not failing. With Cypress 13 this was not the case.
Another error that pop up with Cypress 14 now often is "Element can not be clicked because it is covered by another element". With Cypress 13 these tests all did not run into this error. This is also a consequential error because parts of the webpage do run much slower than before and some components are still visible that should not.
All this only happens in headless mode. Wenn using cypress open and run the Tests in Browser all these tests did not fail even with Cypess 14!
Even if the tests have not yet been written optimally, after the adjustments they all take significantly longer than before, which is of course frustrating because our developers now have to wait even longer for the tests to be executed. Especially because tests run ok with cypress 13.
Is there anyone else whose tests run slower with Cypress 14?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi!
We are updating from Cypress 13 to 14.2
Some Tests are failing with version 14 and we investigate why.
It seems that some of our tests fail because elements are rendered much slower than before. We have to modify the test code to counteract this.
For example we had this test code running fine in Cypress 13
Explanation: Clicking on "more-actions" opens a menu. In this menu we click on "remove-site". This menu is supposed to close after an element in the menu was clicked. By clicking "remove-site" a dialog is shown. We close this dialog by clicking the button labeled "Nein". After that we want to open the dialog again and klick the button labelled "Ja".
With Cypress 14 this part of the test failed with an error that said something like "can not click element because it is already detached from dom".
I had to add
cy.getBySel('remove-site').should('not.exist');
after the firstcy.getBySel('remove-site').click();
to ensure that the secondcy.getBySel('remove-site').click();
is not clicking the first element which was still visible. So the tests runs with Cypress 14 now and the code is as followsAfter "fixing" the test I compared it running in Cypress 13 and Cypress 14. (the modified test code both in 13 and 14)
The test with Cypress 13

Same test with Cypress 14

Some information: I used cy.wait() for testing proposes and had to wait 5 seconds after
cy.getBySel('remove-site').click();
for the menu to disappear and the test not failing. With Cypress 13 this was not the case.Another error that pop up with Cypress 14 now often is "Element can not be clicked because it is covered by another element". With Cypress 13 these tests all did not run into this error. This is also a consequential error because parts of the webpage do run much slower than before and some components are still visible that should not.
All this only happens in headless mode. Wenn using cypress open and run the Tests in Browser all these tests did not fail even with Cypess 14!
Even if the tests have not yet been written optimally, after the adjustments they all take significantly longer than before, which is of course frustrating because our developers now have to wait even longer for the tests to be executed. Especially because tests run ok with cypress 13.
Is there anyone else whose tests run slower with Cypress 14?
Beta Was this translation helpful? Give feedback.
All reactions