E2E test with Cypress fails because of timeout

[denryh]

When I ran a cypress 2e2 test either using its GUI or CLI, I always get time-outed because the image request was too slow after couple of images, and this is only happening in Cypress test, not on my browser.

Here's the picture when I look at the network tab on the browser dev, versus what is going on under Cypress running

This is the browser


.png)

As the picture is showing here, after the 70.png, every png after that got slow down significantly and it cause the test to time-out.

Please tell me why cause I hate it so much already..
Thank you.

[AliAbuSalam]

I had this same issue before. My solution is just to increase page loadout time of cypress from 1 minute to 3 minutes.

[denryh]

Thank you. Yeah, I already increased pageLoadTimeout to 2000ms, usually it needs only 1m8s-1m15s.

Another option is to change the parameter of the fetch uri from getting 784 pokemons to somewhere around 200, which is around the boundary where it starts to slow down.

I think that this is about the config of Cypress or something because when I reload the test even though its redirecting 304 to the assets that was cached or something, they also got slow down too.

Anyway, I just wanna know what is happening..

[artemtsaryov]

Looks like this is an existing performance limitation wth no solution yet: cypress-io/cypress#8156

[mluukkai]

finally fixed