Cypress.io Reviews

Cypress is praised for its easy setup, fast test execution, real-time reloading and debugging capabilities, automatic waiting and retrying, excellent documentation and community support, bundled assertion library, and powerful test capabilities. It offers developers an intuitive API, speeds up test runs, simplifies debugging with time-traveling, and automates waiting and retrying.

It has some areas which are need to be improved including limited browser support primarily for Chromium-based browsers, challenges with cross-domain and iframe interactions, occasional difficulties in debugging complex scenarios, and a steeper learning curve for advanced features. However, with an active community and ongoing development, Cypress continues to evolve and address these concerns, making it a valuable testing framework for many developers.

In my view, Cypress solves problems related to simplified test setup, faster test execution, improved debugging capabilities, automatic waiting and retrying, a developer-friendly API, and comprehensive documentation with community support. These benefits result in time savings, enhanced reliability, improved debugging efficiency, and a positive developer experience.

Cypress is one of the best frameworks I ever used, almost from the beginning of their development. It has good documentation and the possibility to write the plugins that your tests would need

Cypress always improves. Thanks to the big community, it solves all possible cases

e2e and api tests

I love that you can run your test in a browser and see all of them running in real-time. This gives you a great vantage point into your test suites, so you can see exactly where issues may be occurring.

Mocking APIs in Cypress is not always super straightforward and can take some getting used to. I also feel like unit testing could be a bit more intuitive as well.

Cypress helps in two major ways. One, when used in TDD, it ensures the code we write is doing what we it expect it to. And as part of our CI/CD, we are able to ensure new features don't introduce regressions.

Cypress is easy to use, easy to knowledge, easy to find elements to create the tests, and perfectly integrated with Node.Js, and is good too for doing tests of APIs Restful. Much faster and stabilized in comparison to Selenium

- Only Javascript to use;

- Parallel tests is only disposable in pay area;

The create an e2e test to validate the solutions which the team do based on the requirements

I would say that I like the most the documentation provided by the Cypress team and the fact that you can find solutions for hickups on the Internet.

Interacting with the elements using Cypress is easy, and can help writing end to end tests, being able to test both UI and Backend / APIs with Cypress.

I do not have any cons related to Cypress.

Implementing an automation framework via Cypress can reduce the testing times, helping the QA teams to have time to focus on the new features rather than performing regression testing, when Cypress can do it faster and probably more reliable (according to the written automation tests).

Facilidade de configuração do projeto e implementação dos cenários

Não faz conexão com banco de dados, isso atrapalha um pouco

Possibilidade de execução de centenas de testes das funcionalidades antes do deploy.

Easy and fast. It handles component, e2e and api test

It does not work with Safari browser. ..

It automates end to end tests

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.

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

We are using Cypress to automate our testing for website that had zero if any cypress automation. The ease of use and the ability to bring QA team up to speed on using cypress and writing tests has been the greatest benefit so far

Cypress is easy to set up and has multi-faceted solutions for whatever your test needs may be. At first glance, it seems like a one-trick web UI e2e solution. But upon further use you will quickly realized this tool can be used for so much more.

Cypress has its flaws, starting off as a Chrome browser-only solution is a big drawback. Once you get past that and begin using it you will quickly find out they've been hard at work adding more browsers like Firefox and Edge. No mobile support creates a tough choice for some teams if they want to have a one-trick solution for all automated testing.

If you're looking to automate your Web UI or API services this tool can help you achieve it fully. Integrates well with any CI/CD tool and will elevate your release cycle right away.

Web UI automated testing that is quick, lightweight, and reliable. Our e2e test run times were drastically decreased by switching from Nightwatch. Our engineers do not have to wait hours for a full regression to run now, it's able to be completed within an hour.

I love that Cypress allows you to write end-to-end tests in the same way you would write unit and integration tests within the React / Javascript environment. I also love that they integrate with the React Testing Library to make asserts seamless also.

The inability to change domains can be a bit cumbersome (and a blocker) when you're trying to test an application with authentication that is from another vendor like Microsoft.

I am creating general end-to-end testing, as well as mock data-style E2E with mocked API responses via Cypress's mock data feature.