3 ms·
I agree with this, after you get past the simple happy path testing, working with Cypress is mostly just wrestling with Cypress and its limitations. Most of th
by monkpit 3y ago
I agree with this, after you get past the simple happy path testing, working with Cypress is mostly just wrestling with Cypress and its limitations.
Most of the limitations are around 2 things - Cypress has its own JS runtime separate from the node process which causes weird (non-intuitive) behavior. The other thing is the hand-wavy way Cypress tries to pretend the code is not async. You can’t just write JavaScript and have it work the way you expect, you have to write Cypress-flavored JavaScript, which sets up lots of footguns for junior engineers and causes you to have to be extra vigilant on code reviews.
I have worked heavily with Cypress for years, and if I were starting a new project I would 100% choose Playwright.