Cypress does not depend upon so many other testing tools like selenium and web drivers. It also has some additional features like the time travel feature, which helps a lot while debugging the failed tests. It also has a dashboard where users can see test logs. Review collected by and hosted on G2.com.

It is hard to automate web apps with a lot of iframes. Also, cypress has some really annoying issues such as sometimes it says that tests pass without executing all the steps. It has support for dynamic waits (and auto wait), but if I want to call a function recursively if the element that the function search for is not found, by using try-catch-recursive call, call it is not possible to do so. Review collected by and hosted on G2.com.

I no longer feel comfortable shipping apps that aren't tested with Cypress. Even for happy-path spot checks, it has elevated my confidence in shipping new features through the stratosphere. Review collected by and hosted on G2.com.

Browser compatibility has room for improvement, but this has been steadily improving over time. Review collected by and hosted on G2.com.

Mocking flaky services, automatic wait for elements and scrolling into the page. There is a fantastic dashboard for tracking test results. You can see all flaky tests and the pass rate for each test. Lets not forget the retry functionality. Review collected by and hosted on G2.com.

Sometimes there is an exception in the framework and the test passes at the second run. Review collected by and hosted on G2.com.

Cypress is incredibly easy to set up and has everything you need in order to get started on your testing right out of the box. I have not run into a testing scenario that Cypress has not been able to solve from functionality all the way down to performance. Cypress also offers parallelization which has been great for reducing CI build times, which is a huge bonus. Overall Cypress has made testing less of a hassle than any other framework I've used thus far. Review collected by and hosted on G2.com.

It would be nice to have testing life cycle hooks for async tasks such as clearing a database with the built-in ability to wait for the async tasks to complete. It would also be great to have built-in tools for working with file uploads. Review collected by and hosted on G2.com.

- easy to write

- easy to understand

- easy to debug

- covers chrome, and nowadays other browsers. But very much sufficient for developers to move ahead with the release Review collected by and hosted on G2.com.

- sometimes tests are flaky, and we need to retry. Handled this case by configuring .travis to retry on failure. No everyone is happy, when build is happy Review collected by and hosted on G2.com.

So many of the issues and gripes that I have had with Selenium based testing over the years are addressed in Cypress. The default setup is a great start and customization is intuitive and easy to implement. The documentation is some of the best I have ever seen. And the UI makes it easier to reason with test writing and debugging.

I spent 4+ years away from web (testing mobile apps), and it was so refreshing to come back to web testing and see that I will never need to use Selenium again! Review collected by and hosted on G2.com.

When something goes wrong at the Cypress level, it can still sometimes be hard to figure out what has happened. With a quick search, I can usually find a workaround or solution in Github issues given how responsive the team is there. Review collected by and hosted on G2.com.

Cypress makes testing easier and fun. As it's directly embedded in to the browser web testing can be supported with checking for network calls. No other tool provides this feature.

Documentation is super clear and helpful. There's not topic of cypress for which the documentation doesn't exists.

The best part is test runnner. It makes running and debugging cypress tests convenient.

Cypress Community is helpful and growing. Be it linkedIn group or individual slack communities. People are always willing to share the information about cypress.

Cypress is quite modern in terms of running in the CI pipelines or running as a docker container. There are already docker images present on docker hub where you can run your entire test suite with one command.

They recently came out with an awesome feature of slack integration which makes it easier to know the tests runs status without having to navigate to CI/CD pipelines.

The feature that wins and makes cypress the best tool in the market is cypress dashboard. It has all the information about the test runs. Review collected by and hosted on G2.com.

There should be a slack community where we can ask questions/doubts related to cypress. Individual communities do exists and there's also a forum but slack would be cool. I might be wrong and a community might exist already. Review collected by and hosted on G2.com.

Cypress is a great tool for E2E testing. Cypress is easy to setup, if you are using Typescript or JavaScript. Documentation for cypress is one of the best I have seen in my over 20+ years in software development. All the available commands, and the ability to add custom commands improve test structures and allow re-usability of common testing task, for example logging in. The test runner for cypress is amazing, it gives you the ability to run one or more test files, gives you the ability to find issues easy, and full access to developer tools in your tests. Review collected by and hosted on G2.com.

Some of the `paid` only features that can help the community, specifically running test in parallel would be great if that is possible to do locally, or even in the free tier for the Dashboard. As we write more and more tests, some organizations have stricter rules about what tools to use, giving these organization some of these benefits can help the entire community Review collected by and hosted on G2.com.

The ability to stub the network request and clean APIs. The documentation is easy with best practices & anti-pattern warnings Review collected by and hosted on G2.com.

There is no way to rerun only failed tests and UI takes some time to load the tests before running them Review collected by and hosted on G2.com.

I love the way Cypress can handle TDD. It can replace opening Chrome on its own completely. The tests are intuitive to write, have simple API and their execution is so fast that probably 99% of the features are faster to implement by writing a test first than to manually interact with the browser.

API stubbing is great too because it allows creating an isolated environment that does not touch the backend API. This can provide an additional layer of security and efficiency to your development flow. APIs can change, but the front end developers can still develop features using specific data fixtures without creating a full backend mock API clone.

The simplicity of the usage is definitely attributed to the amazing and thorough official documentation. Review collected by and hosted on G2.com.

There is no official "drag and drop" command at the time of writing. There is a workaround by triggering mousedown, mousemove and mouseup event and it works well, but I would prefer a drag command with options parameter so the step count between point A and B can be specified.

Cross-browser support would be a huge upgrade. But, the Cypress team is already working on it so it will probably be available in the close future! Review collected by and hosted on G2.com.