Skill

e2e-testing-patterns

Provides E2E testing patterns for Playwright and Cypress to build reliable test suites, debug flaky tests, test user workflows, and integrate with CI/CD.

Playwright

Cypress

testing

Install

npx claudepluginhub joshuarweaver/cascade-code-general-misc-2 --plugin rmyndharis-antigravity-skills

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Build reliable, fast, and maintainable end-to-end test suites that provide confidence to ship code quickly and catch regressions before users do.

Supporting Assets

resources/implementation-playbook.md

SKILL.md

Similar Skills

using-git-worktrees

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

168.3k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

superpowers

168.3k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

168.3k

Stats

Stars682

Forks124

Last CommitJan 18, 2026

Actions

View Source View Plugin View on GitHub View README

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

Identify critical user journeys and success criteria.
Build stable selectors and test data strategies.
Implement tests with retries, tracing, and isolation.
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.