Comments on the claims of “7 ways Cypress is different”. All False, Wrong or Lie. Part 1: Developer-Focused is Wrong for E2E Testing
E2E Testing tool should be Tester-Focused, not Developer-Focused

This article was originally published on my Medium Blog on 2023-07-08.
On Cypress's website, it claims (still there, as of 2023–07–03).

Most Cypress testers should have known this: more and more people switched (or are about to) to Playwright. When I say something (as a former research scientist and a testing engineer), I will quote results to support my statement. Below are Google results for “cypress playwright migrate” or “playwright cypress migrate”.

See the movement! There is one Reddit post from the Google results with the title “Cypress.io is about to die, you should migrate your projects”.
“But Cypress is most likely going to close down soon. …
They were already having trouble converting free users to paid users, but then Playwright came along and literally destroyed them.…
A lot of folks hated Cypress because it was limited, you had to pay up in order to properly integrate it into your pipeline. …
The propaganda Cypress did to promote their tool is literally taken out of the Soviet Propaganda manuals.” — source
“Cypress is literally dead. Playwright came and took their lunch.” — another Reddit post said in a funny way.
Here I want to point one thing out, most comments above are referring to Cypress as the company and its behaviour, and only one is about the technical aspect of the tool. Here I am not speculating the future of Cypress.io (a downsizing announcement in Jan 2023 is real though, used the phrase ‘incredibly difficult, but necessary’ for the decision), only see Cypress as a technical failure as a test automation framework/tool.
Let me quote the conclusion of another article, which I read in my Medium feed last week.
“Conclusion
Migrating from Cypress to Playwright can significantly improve your end-to-end testing experience, offering better developer experience, faster test execution, and improved test stability” — from Luc Gagan’s article “Migrating from Cypress to Playwright”
So, the so-called “most developer-loved” is FALSE, i.e. failed assertion, at least lost to Playwright in the JS community alone. In this article, I will talk about Cypress’s “Soviet propaganda” that the Reddit post refers to.
The Developer-Focused End-to-End Testing is Wrong, Obviously
There is a fundamental error in the mindset behind that statement: End-To-End Testing is not about the developers, instead, its audience is the whole team.
Since college, I was taught “end-to-end functional testing is a black-box testing, shall be done independently from developers”, and pretty much what I witnessed in my career. (I know some will say something about new Shift-Left testing, read on). In some Waterfall teams, testers are not allowed to talk to developers and conduct testing strictly based on the specification.
Some will say “We do Agile”. I know Agile well.

According to Kent Beck, Father of Agile, a real Agile team must have the technical capability to do daily production releases. I have been doing that for some client projects since 2008 and my own apps since 2012. Some long-time readers have read and seen test reports (running a big number of Selenium WebDriver tests as regression testing on a daily basis). This is not a show-off but rather to talk about real test automation from a successful Agile perspective.
Developer-loved test automation tools are often a bad choice. For example, during 1997–2015, Java was the dominant coding language. Many developers, including me (for a short while), wanted to use it for testing too. Thankfully, I met one world-renown top Java programmer, who pointed out an obvious thing, “test script should be in a scripting language”. I discovered Ruby, Wow! I think some Microsoft C# developers probably loved Microsoft Coded UI (using the same language and visual studio IDE), but it was deprecated in 2018.
Some would argue, “JavaScript is a scripting language”. Not long ago, Angular.js was the most popular web development framework, and its associated testing tool Protractor became hugely popular. Angular developers sure would love Protractor, as it has built-in support with Angular model in the test syntax, Can’t beat that! The result: Protractor was deprecated.
Software Testers’ job is to find developers’ defects. “Developer-Loved” and “End-to-End Testing”, when these two terms are used together, sounds not completely impossible, but does not feel right, does it?
--
In Part 2, I will comment on Cypress's seven claims one by one.
About the Creator
Zhimin Zhan
Test automation & CT coach, author, speaker and award-winning software developer.
A top writer on Test Automation, with 150+ articles featured in leading software testing newsletters.



Comments
There are no comments for this story
Be the first to respond and start the conversation.