E2E Test Generator
When to Trigger
- •Critical user flows
- •"Test checkout flow"
- •Multi-step processes
What to Do
- •Flow: Login (or use fixture), navigate, fill forms, submit, assert URL and success message.
- •Selectors: Prefer data-testid or role/label; avoid brittle class/text when possible.
- •Assertions: Visible text, URL, disabled state; wait for navigation or network if needed.
- •Variants: Validation errors (submit empty), error states (e.g. unavailable item).
Use project E2E runner (e.g. Playwright). Keep one flow per describe; use beforeEach for login. Document required test user/env.