Hacker Newsnew | past | comments | ask | show | jobs | submit | cageling's commentslogin

I agree! Thanks for posting the link to Github issue, I was looking for one to also voice my thoughts. We are also one of the companies affected and I just spent the entire day researching alternatives and planning future moves.

For now we'll unblock ourselves with the modified binaries workaround, but who knows when we'll get blocked without any warning again? Unfortunately migrating to something else will not be easy for us (over 1.2k complex test cases written in 200+ spec files). In the meantime we'll probably have to limit number of tests runs and migrate to Cypress.io before we do any moves towards Playwright.

I'd love to hear your thoughts on Playwright. I constantly hear amazing things about it and there are issues with Cypress that really frustrate me (ekhem Cypress.Chainable...). Have you encountered any significant flake with Playwright? How easy it is to debug and solve?

Thanks!


Briefly, we've found Playwright to be easier to implement (exception: Vue and component testing which is functional, but experimental and not well documented), easier to target, faster, and less flaky.

FWIW, GitHub Copilot is great at helping refactor tests.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: