Test Feature

Validate a finished or nearly finished feature through the real product surface, capture evidence, and write a local HTML report. This is the human-facing QA workflow. Use agent-browser for low-level browser mechanics and automate-e2e-tests when the validated behavior needs durable regression coverage.

This is the generic starter skill. In real projects, run setup-task-to-pr first so this skill can be enriched with local URLs, auth, devices, commands, report paths, and surface-specific rules.

When Not to Use

• Do not use before the feature is implemented enough to exercise.
• Do not use for pure API checks without user-facing behavior unless the project has no UI; configure test-api-feature if API validation is common.
• Do not use for authoring automated E2E tests. Use automate-e2e-tests.
• Do not use for low-level browser operation alone. Use agent-browser.
• Do not use for broad flaky-suite repair or test infrastructure cleanup.

Inputs

Read: