Cypress vs Selenium & Getting started with Cypress
Cypress.io aka Selenium Killer has become the current trend in test automation. It has been able to standout from Selenium featuring better performance in many aspects. Let’s first speak on the current situation before getting in to the depth..
Before I go into this, I want to emphasize that this post is not about one particular project or any automation testers that I have worked with. I have experienced this behavior in a recent project with 10,000+ test cases.
Majority of the test automation engineers has written in selenium despite nearly everyone having a pretty grim experience due to the inherent known issues that I will state later.
Selenium tests might be difficult to write, but they are straightforward to copy and paste, which will, of course, lead to all sorts of problems.
We often hear, “If it moves, write a selenium test for it”. Automation tests must be written for the API, the frontend, the backend, the middle-end, the happy path, the sad path, the upside-down path, etc.
We won’t have any time for manual testing, how could we? We have all these flakey selenium tests to write and maintain. We are already late for this sprint, and every story must have an automation test.
After a year or so and an insanely long build, we will decide that this was a bit silly and delete them all or, worse, start again.
