Exit Strategy for Cypress Testers
Another familiar situation for JavaScript Testers (PhantomJS → WebDriverIO → Protractor → TestCafe → Puppeteer → Cypress → ?)
Non-Medium members: Read this article free on Substack, my main blogging platform now.
In the preceding article titled “Cypress.io is Dying”, I gathered factual information and financial figures to substantiate this perspective. Based on the facts & information presented, it is evident that the collapse of Cypress.io (the company) is not merely a rumour but a matter of time. The question for many current ‘cypress testers’ may be thinking, “What shall I do?” Of course, these people don’t really care about Cypress.io or the Cypress product, they care about their next jobs.
In this article, I will share my suggestions (as always, freely free to ignore them). Some who read my prediction of Cypress nearly three years ago and followed my advice might find themselves in a good position.
Table of Contents:
· What are the options for current Cypress testers?
∘ 1. Do nothing, pretend not hearing anything.
∘ 2. Migrate to Playwright, like most
∘ 3. Migrate Cypress API Testing to Ruby API Testing
∘ 4. Upgrade to learn Selenium WebDriver to do real
· FAQ
