OpenHands e2e-testing
This skill should be used when the user asks to "add an E2E test", "run live E2E", "run mock-LLM tests", "debug Playwright CI", "test the Docker image", or changes tests/e2e, Playwright configs, E2E workflows, artifacts, or test reporting.
install
source · Clone the upstream repo
git clone https://github.com/OpenHands/OpenHands
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/OpenHands/OpenHands "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.agents/skills/e2e-testing" ~/.claude/skills/all-hands-ai-openhands-e2e-testing && rm -rf "$T"
manifest:
.agents/skills/e2e-testing/SKILL.mdsource content
End-to-End Testing
Use the correct test layer and preserve the security and production-fidelity boundaries between ordinary browser tests, mock-LLM suites, Docker image tests, and live LLM-backed QA.
Workflow
- Read
before changing any E2E framework file or debugging an E2E failure.references/guide.md - Select the cheapest suite that exercises the real changed boundary.
- Keep live credentials isolated to trusted execution steps and prevent analytics or sensitive artifacts.
- Diagnose CI failures from workflow summaries and Playwright artifacts before modifying locators or timeouts.
- Follow the repository testing rules: cover behavior through real code paths, minimize cases, and mock underlying services rather than hooks.
Reference
— Live and mock-LLM architecture, Docker mode, local commands, CI/reporting security, artifact debugging, common failure patterns, and general testing rules.references/guide.md