/e2e-gen

Skip the boilerplate — describe a flow, get a working Playwright test.

Usage

What it does

1. Reads your playwright.config.ts to understand baseURL, projects, fixtures
2. Looks at existing tests in tests/ to match conventions
3. Maps your description to selectors using:
   • Routes from your app router
   • Text content from your components
   • Test IDs (data-testid) where present
4. Writes a complete .spec.ts file with:
   • Setup (login fixture if needed)
   • Steps with proper waits (waitForURL, expect().toBeVisible())
   • Assertions at each milestone
   • Cleanup

Conventions enforced

• One test per scenario (no nested describes for unrelated flows)
• expect() after every navigation
• Real selectors > XPath
• No hardcoded setTimeout — use Playwright's auto-waiting
• Strict mode safe (use .first() / .getByRole to avoid violations)

Output location

tests/<feature>.spec.ts (or wherever your config points)

Rules

• Don't generate tests for flows the user hasn't described — surface gaps instead
• If a flow needs auth/seed data, scaffold the fixture too
• Add a comment at the top: // Generated by /e2e-gen — review before committing