Use Autohand Code with web app testing skill guidance to add browser tests for login, checkout, admin, or other critical flows.
Verify critical browser flows end to end
Testing Quality and review Verification Testing
autohand -p "Add E2E coverage for this browser flow using the existing test setup"
Browser-level tests for the critical path with stable selectors and setup notes.
Add E2E web tests with Autohand Code is a browser-verification workflow that adds end-to-end tests for critical user paths using existing Playwright or web testing conventions. ### At a glance | Question | Answer | | --- | --- | | Best for | login, checkout, onboarding, admin actions, settings flows, and regressions that only appear in a browser | | Primary inputs | User flow, route, and expected states; Existing E2E setup, seed data, and test command; Stable selectors, auth setup, and environment requirements | | Autohand Code returns | Browser-level tests for the critical path with stable selectors and setup notes. | | Avoid when | a unit or integration test can prove the behavior with less setup and lower flake risk | ### How Autohand Code handles this workflow 1. Finds the current browser test framework and fixture strategy. 2. Adds stable selectors or uses accessible locators where project patterns allow it. 3. Covers the primary path and a high-value failure or empty state. 4. Runs the focused E2E command and reports flake risks. ### Best inputs - User flow, route, and expected states - Existing E2E setup, seed data, and test command - Stable selectors, auth setup, and environment requirements ### Strong prompt autohand -p "Add E2E coverage for this browser flow using the existing test setup" ### Autohand Code CLI options - Use `/skills use webapp-testing` before adding browser tests. - Run `autohand -p "Add E2E coverage for this browser flow using the existing test setup"` with the route and state requirements. - Use `--auto-mode` only after the local app and test command can run repeatably. ### Review before accepting Review stable selectors, setup and cleanup, screenshots or traces when useful, and a passing focused E2E command. ### Source and validation signals Autohand AI maintains this workflow as first-party product guidance for Autohand Code. Use the [Autohand CLI Playbook](https://github.com/autohandai/code-cli/blob/main/docs/AUTOHAND_PLAYBOOK.md), [CLI reference](/docs/working-with-autohand-code/cli-reference.html), and [configuration reference](https://github.com/autohandai/code-cli/blob/main/docs/config-reference.md) when choosing between interactive mode, command mode, auto-mode, feature-enabled /goal, /settings, skills, MCP, and permission settings. The related resources below link to product docs and tutorials for the workflow, and the final answer should name repository-specific files, commands, outputs, or docs that a reviewer can verify. ### Frequently asked questions ### What is Add E2E web tests with Autohand Code? Add E2E web tests with Autohand Code is a browser-verification workflow that adds end-to-end tests for critical user paths using existing Playwright or web testing conventions. ### When should a team use Add E2E web tests? Use it when real browser behavior is the only reliable proof for a user-facing flow. ### What evidence should reviewers check for Add E2E web tests? Review stable selectors, setup and cleanup, screenshots or traces when useful, and a passing focused E2E command.
Skill Skilled: Web App Testing Use browser testing and verification patterns. https://skilled.autohand.ai/skill/webapp-testing Tutorial Add Integration Tests to an API Extend lower-level coverage before E2E where useful. /docs/tutorials/add-integration-tests.html Tutorial Build a Testing Agent Create reusable test workflows. /docs/agent-sdk/tutorials/600-testing-agent.html