pw-to-vitest

To migrate Playwright tests to Vitest, you convert `.test.ts` and `.driver.ts` files into Vitest's `.browser.tsx` format. This process adapts Playwright's interaction and assertion patterns to the Vitest Browser API.

Converting Playwright component tests to Vitest browser mode involves transforming test file structures, imports, locators, and setup interactions into the Vitest Browser API format. This specifically targets component test suites for migration.

Yes, the Vitest Browser API replaces Playwright interaction patterns by adapting file structures, imports, locators, and assertion logic. It transforms existing test files into the `.browser.tsx` format required for Vitest browser mode.

When migrating to Vitest, Playwright `.driver.ts` files are converted alongside `.test.ts` files into the `.browser.tsx` format. This conversion adapts your existing test setup and interaction drivers to the Vitest Browser API.

Yes, converting Playwright assertions to Vitest requires changing file imports and adapting test setup patterns. The migration process adjusts imports, locators, and assertions to match the Vitest Browser API format.

You should migrate component tests from Playwright to Vitest when streamlining your testing framework, specifically targeting directories like `libs/components/src/`. This migration converts existing test files and drivers to the Vitest Browser API.