DEV Community

loading...
Cover image for Why you should use Cypress for test automation

Why you should use Cypress for test automation

Walmyr Filho
I'm a software engineer that loves testing. I'm also a clean coder, blogger, YouTuber, Cypress.io Ambassador, writer, online teacher, mentor, consultant, speaker, an active member of tech communities.
Updated on ・4 min read

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.


This post was translated to Portuguese, and it can be found on the Talking About Testing blog.


Would you like to learn about test automation with Cypress? Get to know my online courses on Udemy.

Discussion (2)

Collapse
rosariotech profile image
Richard Rosário

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.

Collapse
walmyrlimaesilv profile image
Walmyr Filho Author

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.