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.
소스 정보
- 저장소
- OpenHands/OpenHands
- 최근 소스 활동
- 2026년 10월 16일 17:45
- 감지된 SKILL.md 언어
- 영어
- 스타
- 91,837
- 포크
- 12,195
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
파일 탐색기
2 개 파일SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- e2e-testing
- description
- 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.
# 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
1. Read `references/guide.md` before changing any E2E framework file or debugging an E2E failure.
2. Select the cheapest suite that exercises the real changed boundary.
3. Keep live credentials isolated to trusted execution steps and prevent analytics or sensitive artifacts.
4. Diagnose CI failures from workflow summaries and Playwright artifacts before modifying locators or timeouts.
5. Follow the repository testing rules: cover behavior through real code paths, minimize cases, and mock underlying services rather than hooks.
## Reference
- **`references/guide.md`** — Live and mock-LLM architecture, Docker mode, local commands, CI/reporting security, artifact debugging, common failure patterns, and general testing rules.
GitHub에서 보기