generate

Topics in the source

• Generate Playwright Tests
• Input
• Steps
• 1. Understand the Target
• 2. Explore the Codebase
• 3. Select Templates
• 4. Generate the Test
• 5. Match Project Conventions

Generate production-ready Playwright tests from a user story, URL, component name, or feature description. $ARGUMENTS contains what to test. Examples: "user can log in with email and password" "the checkout flow" "src/components/UserProfile.tsx" "the search page with filters" Parse $ARGUMENTS to determine: User story: Extract the behavior to verify Component path: Read the component source code Page/URL: Identify the route and its elements Feature name: Map to relevant app areas Use the Explore subagent to gather context: Read playwright.config.ts for testDir, baseURL, projects Check existing tests in testDir for patterns, fixtures, and conventions If a component path is given, read the component to understand its props, states, and interactions Check for existing page objects in pages/ Check for existing fixtures in fixtures/ Check for auth setup (auth.setup.ts or storageState config) Check templates/ in this plugin for matching patterns: | If testing... | Load template from | |---|---| | Login/auth flow | ../pw/templates/auth/login.md | | CRUD operations | templates/crud/ | | Checkout/payment | templates/checkout/ | | Search/filter UI | templates/search/ | | Form submission | tem

This is an excerpt. Refer to the complete source and its current requirements.