While Cypress excels at simple demos, it falls apart with real-world complex applications. The 'runs in browser' approach creates constant flaky tests due to timing issues and iframe limitations. For enterprise applications with multiple domains, the workarounds become so cumbersome that you spend more time fighting the tool than writing tests. The documentation feels misleading about these real-world limitations.
Cypress has completely transformed how our team approaches frontend testing. The ability to write tests in JavaScript and see them run directly in the browser makes debugging incredibly intuitive. The automatic waiting and real-time reloads eliminate so many of the flaky test issues we had with other frameworks. The dashboard service is worth every penny for our CI/CD pipeline.
As a developer tired of flaky Selenium tests, Cypress has been a revelation. The real-time reloads, automatic waiting, and intuitive debug tools make writing and maintaining tests straightforward. Running directly in the browser eliminates countless sync issues I used to wrestle with.
For all the hype around Cypress, I've found it to be a constant battle. The in-browser architecture is great when it works, but dealing with flaky tests from the dreaded 'detached DOM element' errors and working around the same-origin policy for iframes is a nightmare. Setting up and managing the test runner on multiple projects has been more complex than advertised, with inconsistent behavior between environments slowing our whole team down. Debugging tests often feels like fighting the tool rather than testing our app.
As a developer who previously struggled with flaky Selenium tests, Cypress has been a revelation. The ability to see exactly what the test sees in real-time, with automatic waiting and detailed error messages, has cut our debugging time in half. The API is intuitive and the documentation is excellent, making it easy for our whole team to contribute to test coverage. It just works the way you'd expect a modern testing tool to work.
I really appreciate the speed and how Cypress runs natively in the browser, making tests feel very fast and the debugging experience is fantastic. The ability to time-travel and see the state of the application at each step is a game-changer for debugging flaky tests. However, the initial setup and configuration, especially for more complex projects, has a steep learning curve. It's incredibly powerful for E2E and component testing, but the learning curve and the cost for the Dashboard service can be a hurdle for smaller teams.
After migrating our enterprise test suite to Cypress.io, we've hit constant roadblocks with its limitations on multiple tabs and cross-domain testing. The chrome-only execution feels restrictive when we need to validate legacy browser support, and test flakiness has increased dramatically with dynamic content. While it's great for simple scenarios, real-world complex applications expose too many gaps in its architecture.
Cypress.io has completely transformed how we handle front-end testing. The ability to write and run tests directly in the browser makes debugging incredibly intuitive, and the real-time reload feature saves so much time. The documentation is excellent, and the built-in wait handling eliminates the flakiness we struggled with in other tools. It's become an essential part of our development workflow.
Cypress has been a game-changer for writing reliable front-end tests that run directly in the browser; the test runner UI is fantastic for debugging. However, its architecture means you can't easily test multiple domains or tabs, which is a deal-breaker for some of our workflows. The documentation is good, but troubleshooting flaky tests in CI can be a real time-sink.
Cypress.io initially won me over with its clean interface and fast in-browser execution. However, as our application grew more complex, it became painfully clear that its lack of support for multiple tabs and its restrictive same-origin policy are deal-breakers. The inability to test certain cross-domain workflows or interact with external authentication providers means we're constantly writing workarounds, which defeats the purpose of a streamlined testing tool. For a modern web application, these limitations feel archaic and significantly slow down our development cycle.
Based on 12 reviews
Cypress.io is an open source, front end testing tool built for the modern web. It allows you to write automated …
Back to Product