Playwright End-to-End Test Suite Generator

What it does

/e2e-suite is a Cursor slash command. Type it in chat to run a saved workflow: Playwright End-to-End Test Suite Generator.

Generates comprehensive Playwright automated test suites covering critical user journeys (signup, onboarding, Stripe checkout, workspace management).

Automated browser tests covering signup, checkout, settings, and auth. Unlike a skill, a command is something you invoke on purpose. The agent does not decide to run /e2e-suite for you.

Why it exists

Founders retype the same multi-step prompt until it rots. /e2e-suite exists so the pipeline, all 4 steps of it, is a file in .cursor/commands, versioned with the repo.

It ships in the Engineering Kit. It is wired to the Test Automation Engineer (test-automator) and React 19 & Next.js Specialist (react-specialist) agents. Required skills: Playwright End-to-End Browser Testing; Vitest Unit & Integration Testing.

When to use it

• Use to safeguard revenue-critical product workflows against regression bugs.
• Use /e2e-suite when you want that pipeline, not a freeform chat. If you only need one step, use a narrower command or a single agent.
• Start a new chat. Do not run this command in a thread that just wrote marketing copy.

When not to use it

• Do not run /e2e-suite as a substitute for reading the diff. The command produces files; you still gate them.
• Do not chain it into a 40-turn chat. Fresh context is part of the design.
• Do not run it if you have not filled CURSOR.md. The pipeline will invent a stack.

Example workflow

1. Configure playwright.config.ts with multi-browser and mobile viewport targets
2. Create reusable authentication state fixtures to bypass repetitive logins
3. Write resilient user journey tests targeting accessible ARIA locators
4. Add visual regression screenshots and CI test reporting

Example usage

Type this in Cursor chat: /e2e-suite Write Playwright E2E test for user signup and Stripe checkout redirect

The command file tells the session which agents to adopt and which skills to read. You should see phase headers, not a single dump of code.

If a phase fails its gate, stop. Do not add 'just continue'.

Example output

• Expected artifact: tests/e2e/auth.spec.ts
• Expected artifact: tests/e2e/checkout.spec.ts
• Expected artifact: playwright.config.ts

Best practices

• Keep the prompt specific. /e2e-suite Write Playwright E2E test for user signup and Stripe checkout redirect is the shape: object, constraint, and outcome.
• Let the listed agents work in order: test-automator → react-specialist.
• Save outputs in the repo. Chat-only answers evaporate.
• Engineering commands should leave tests or an audit note, not only implementation files.

Common mistakes

• Typing /e2e-suite with no object ('do the thing'). The pipeline will guess.
• Re-running the command in the same chat after a failed gate instead of fixing the failing file.
• Editing the command file to skip review so it 'goes faster'.
• Skipping the Playwright End-to-End Browser Testing skill that the command depends on.