Playwright comparison

[sand4rt]

Clear and concise description of the problem

As a developer using Vitest, I want to be able to read a Playwright comparison so that I understand which tool to use in which situation.

Suggested solution

Playwright is a fairly new testing and automation framework from Microsoft, developed by the same team that created Puppeteer. It supports various programming languages and testing types such as end-to-end, API, UI component and unit tests all within a single tool and a single API.

TODO: add comparison

• Uses Vite
• Similar API to Vitest and Jest
• Simular feature/tool set as Cypress
• Fast, executes optionally in a real browser
• VS Code integration like Jest and Vitest
• Parallel tests optionally over multiple machines with sharding
• No smart & instant watch mode yet
• No out-of-the-box code coverage yet

Validations

• [X] Follow our Code of Conduct
• [X] Read the Contributing Guidelines.
• [X] Read the docs.
• [X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[madurapa]

What is the status of this?

[mekwall]

I use Playwright for end-to-end testing and vitest for unit and integration testing. The reasoning here is that vitest is much better suited for unit and integration testing as it can leverage testing library to render ui components outside of a browser environment. It also features watch functionality which is essential when doing test-driven development. As a bonus it is much faster than Playwright.

[cub]

And now Vitest has "browser mode" which launches Playwright (or webdriverio). What are the interests of launching the tests via Vitest and not directly via Playwright ?