`cy.visit` in 3.3.1 is 2x-4x as slow as 3.2.0
See original GitHub issueCurrent behavior:
Running my tests in 3.2.0 takes 1 hour 54 minutes. Running my tests in 3.3.1 takes 4 hours 41 minutes.
(This is running on headless electron using cypress.run
with the module API; I haven’t measured it with cypress open
).
Both cases are running on the same WIndows 10 VM, and not using parallelization.
Desired behavior:
I’d like my tests to take less than 2 hours.
Versions
Cypress 3.3.1
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:37 (15 by maintainers)
Top Results From Across the Web
visit - Cypress Documentation
Pass in an options object to control the behavior of cy.visit() . By default, the cy.visit() commands' will use the pageLoadTimeout and baseUrl...
Read more >Cypress - cy.visit() failed trying to load - Stack Overflow
In my case, it was a slow running test that triggered a timeout of cypress itself. I could fix it by increasing the...
Read more >cypress-io/cypress - Gitter
When using Cypress version 3.3.1 I can't get both themes to work. ... async function () { cy.visit('https://example.com'); await loginActions.
Read more >8 common mistakes in Cypress (and how to avoid them)
... is too slow? Feels like using cy.wait() is the way to go. // ❌ incorrect way, don't use cy.visit('/') cy.wait(10000) cy.get('button') ...
Read more >Cypress cy.intercept Problems - Gleb Bahmutov
visit command. By the time cy.intercept runs, the call is already in progress, and thus not intercepted. Cypress shows XHR calls by default...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@danceric0919 We have a fix in place, it will be out with the next patch release (3.3.2).
We’re triangulating a few different issues in the
3.3.x
releases and several may all be related to the same underlying problem. Likely will have a patch in the next few days and then we can go from there.