comparar · Tests
Both work with Vue, Nuxt. In a kit you pick one, and your agent gets the rule to use only that one.
| Playwright | Vitest + Vue Test Utils | |
|---|---|---|
| What it is | End-to-end tests in real browsers. | Vue component tests with the official Vue Test Utils. |
| Frameworks | Next.js, Vue, Nuxt, Svelte, SvelteKit, Astro, React, Vanilla | Vue, Nuxt |
| Paquetes | — | — |
| Skill oficial | microsoft/playwright-cli@playwright-cli, currents-dev/playwright-best-practices-skill@playwright-best-practices | — |
| How your agent uses it | End-to-end tests go in `e2e/`. Run them with `npm run test:e2e` (it starts the app for you). Use role and text selectors (`getByRole`), not CSS classes. | Use mount from @vue/test-utils with Vitest and a DOM environment. Nuxt runtime composables need @nuxt/test-utils; keep plain unit tests separate from Nuxt runtime tests. |
| Kits that offer it | blog-astro, chrome-extension, desktop-electron, desktop-tauri, docs-fumadocs, docs-starlight, docs-vitepress, landing-astro, landing-next, landing-nuxt, landing-sveltekit, mobile-ionic-react, portfolio-astro, saas-ai-next, saas-next-better-auth, saas-next-supabase, saas-nuxt, saas-sveltekit, saas-t3, saas-tanstack-start, spa-vite-react, web-astro, web-next, web-nuxt, web-react-router, web-sveltekit, web-tanstack-start, web-vue-vite | chrome-extension, docs-vitepress, landing-nuxt, saas-nuxt, web-nuxt, web-vue-vite |
| Chosen in | 0 installs | 0 installs |