Playwright doesn't have a good component testing story yet though. It really needs to come out of beta into mainline.
At this point, its the only reason I use Cypress, as E2E testing via Playwright is a joy to write
At this point, its the only reason I use Cypress, as E2E testing via Playwright is a joy to write
Vitest is also adding browser support of this nature and if that hits enough maturity its all moot anyway
is component testing from cypress really needed. the only "benefit" I see is using a single tool
RTL is great, but jsdom and similar solutions have limitations, being able to run similar tests in live browsers is really validating, in many cases allows us to cut down on writing somewhat more brittle E2E tests
The biggest win with playwright its like writing vitest / jest tests, it uses a similar `expect` function (I believe its a modified version of Jest expect but that may have changed) and I like their Pages API
The only thing I haven't used Playwright for yet is API testing
[0]: as you get more than just a DOM tree snapshot, you get the styles too. Great for catching regressions
Both Cypress and Playwright can use vite out of the box, on the other hand. I like this, since I can use the same configuration for production for running tests (we do this to run tests against prod builds)
Its more overhead currently than I want to take on.