Cypress users lack control over test timing and order
Cypress users report slow suites when navigation waits for the window load event even though the DOM is already usable. They also want to slow commands while debugging and control spec order. The reported workarounds—adding delays command by command and using numbered folders—are awkward; the requests span several years, so their current relevance needs validation.
For cypress end-to-end test developers. Mentioned from Sep 2016 to Mar 2022 on GitHub.
7 different people described this problem in 4 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 5.4/10
- Frequency
- 7.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- High
What people said
Quoted word for word. Follow a link to read the whole discussion.
This would be incredibly helpful for my tests as well - DOMContentLoaded will succeed, but window:load will not
I am a newbie to Cypress. And trying to use it on our site that has lots and lots of blocking scripts & images which delays the onload event to trigger. If this feature - of completing cy.visit() on DOMContentLoaded event is available, it would be great
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 3 places to find your first customers
- 5 more quotes from people who have this problem
- Current workarounds, existing solutions and risks