multiAI Summary Pending
e2e-testing-patterns
Build reliable, fast, and maintainable end-to-end test suites that provide confidence to ship code quickly and catch regressions before users do.
28,273 stars
bysickn33
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/e2e-testing-patterns/SKILL.md --create-dirs "https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/main/plugins/antigravity-awesome-skills-claude/skills/e2e-testing-patterns/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/e2e-testing-patterns/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How e2e-testing-patterns Compares
| Feature / Agent | e2e-testing-patterns | Standard Approach |
|---|---|---|
| Platform Support | multi | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Build reliable, fast, and maintainable end-to-end test suites that provide confidence to ship code quickly and catch regressions before users do.
Which AI agents support this skill?
This skill is compatible with multi.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# E2E Testing Patterns Build reliable, fast, and maintainable end-to-end test suites that provide confidence to ship code quickly and catch regressions before users do. ## Use this skill when - Implementing end-to-end test automation - Debugging flaky or unreliable tests - Testing critical user workflows - Setting up CI/CD test pipelines - Testing across multiple browsers - Validating accessibility requirements - Testing responsive designs - Establishing E2E testing standards ## Do not use this skill when - You only need unit or integration tests - The environment cannot support stable UI automation - You cannot provision safe test accounts or data ## Instructions 1. Identify critical user journeys and success criteria. 2. Build stable selectors and test data strategies. 3. Implement tests with retries, tracing, and isolation. 4. Run in CI with parallelization and artifact capture. ## Safety - Avoid running destructive tests against production. - Use dedicated test data and scrub sensitive output. ## Resources - `resources/implementation-playbook.md` for detailed E2E patterns and templates.