Automate E2E Tests

Turn a validated behavior into durable regression coverage using the project's E2E, integration, contract, or mobile test framework. This is a generic starter skill; project teams should run setup-task-to-pr to enrich it with exact paths, commands, fixtures, auth, device setup, and CI rules.

When Not to Use

• Do not use for manual QA, screenshots, video, or validation reports only. Use test-feature.
• Do not use for broad flaky-suite repair or skip audits unless the user asks for suite maintenance.
• Do not use when unit, component, API, parser, validator, or contract tests are the better level of coverage.
• Do not add E2E tests for docs-only or internal refactors with no user-observable behavior.

Inputs

Before editing tests, read: