Let's be honest. Developers hate end-to-end (e2e) tests.
But this is because they haven't used Cypress.io yet.
Cypress is the most developer-friendly testing framework ever made.
With Cypress, writing tests is a joy!
No configuration is needed to get started. All unit testing tools that you're already familiar with are packaged in. You can write not only e2e tests, but also, unit, component, API, snapshot testing, and even a mix of them all.
Do you need to isolate the frontend from the backend? There we go! With Cypress, you can do it easily.
So, what are you waiting for? Give it a try. You won't regret it, I promise.
Cypress, because the web has evolved. Finally, testing has too.
Get to know the "Pinches of Cypress" series.
- How to fill out and submit forms with Cypress
- How to check that I was redirected to the correct URL with Cypress
- How to run a test multiple times with Cypress to prove it is stable
- How to test APIs with Cypress
- How to check that an element does not exist on the screen with Cypress
- How to protect sensitive data with Cypress
- How to create custom commands with Cypress
- How to visit a page that is on my computer with Cypress
- How to wait for a request to finish before moving on with Cypress
- How to identify an element by its text with Cypress
- How to run tests in headless mode with Cypress
- How to intercept and mock the response of an HTTP request with Cypress
- How to use fixtures with Cypress to isolate the frontend tests
- How to check the contents of a file with Cypress
- How to perform visual regression tests with Cypress and Percy
- How to run tests simulating mobile devices with Cypress
- How to perform an action conditionally with Cypress
- How to take screenshots of automated tests with Cypress
- How to simulate errors with Cypress
- How to simulate the delay in a request with Cypress
- How to type and press ENTER with Cypress
- How to read the browser's localStorage with Cypress
- How to change the baseUrl via command line with Cypress
- How to upload files with Cypress
- How to test that cache works with Cypress
- How to check multiple checkboxes at once with Cypress
- Using the keywords Given/When/Then with Cypress but without Cucumber
cy.requestvs.cy.intercept- Best practices in test automation with Cypress
- How to create fixtures with random data using Cypress and faker
- The importance of testability for web testing automation
- How to login programmatically with Cypress
cy.get()vs.cy.contains()- Testing copy to clipboard with Cypress
- Filtering the available browsers in Cypress
- Simulating Internet Outage and Recovery using Cypress
- Logging into different environments with Cypress
Would you like to learn about test automation with Cypress? Get to know my online courses on Udemy.
This post was translated to Portuguese, and it can be found on the Talking About Testing blog.
Top comments (2)
I used to write protractor tests and now I'm writing cypress tests. Don't need to know that I'm very happy. A suite of tests that I used to take 1 week to develop, using cypress I can deliver in a couple of days.
Same here. I’ve worked with Protractor for around five years. Working with Cypress, things are so much easier, besides all the other possibilities it offers, that other Selenium-based frameworks lacked for so long, especially in terms of dev experience.