Automated summary
This skill provides patterns for building, stabilizing, and running reliable end-to-end test suites, including running them in CI.
Strengths
- Lays out a four-step workflow: identify critical user journeys, build stable selectors and test data, add retries/tracing/isolation, then run in CI with parallelization and artifacts
- Directly targets flaky tests and prescribes robust selector and test-data strategies
- Includes safety guardrails: no destructive tests against production, dedicated test accounts and data, scrubbed sensitive output
- Points to an implementation playbook for detailed patterns and templates
Limitations
- Does not ship ready-to-use code or configuration in SKILL.md itself; details live in resources/implementation-playbook.md
- Deliberately excludes unit and integration testing from scope
- Assumes an environment that can support stable UI automation and provisioned test accounts
Use it when setting up or hardening an end-to-end test suite for critical user workflows, including within a CI/CD pipeline.
Avoid it when you only need unit or integration tests, or when the environment cannot support stable UI automation with safe test accounts and data.
Security analysis
SafeThe skill contains only high-level guidance for end-to-end testing and explicitly advises against destructive tests in production. It does not declare or invoke any tools, scripts, network operations, or commands, and there is no exfiltration or unsafe action.
No concerns found
How this analysis is madeExamples
Our Playwright E2E suite fails randomly about 20% of the time in CI. Help me identify likely causes and rewrite the tests with stable selectors, proper isolation, and retries.Set up an end-to-end test pipeline for our checkout flow: choose the critical journeys, structure the test data, and configure CI with parallelization and trace artifact capture.Add cross-browser and accessibility checks to our E2E suite for the signup and login flows, using dedicated test accounts instead of production data.name: e2e-testing-patterns description: "Build reliable, fast, and maintainable end-to-end test suites that provide confidence to ship code quickly and catch regressions before users do." risk: safe source: community date_added: "2026-02-27"
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.mdfor detailed E2E patterns and templates.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/e2e-testing-patterns-mrwakczu/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/e2e-testing-patterns-mrwakczu' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/e2e-testing-patterns-mrwakczu/download' --output '.skill-downloads/e2e-testing-patterns-mrwakczu/SKILL.md.part' && mv '.skill-downloads/e2e-testing-patterns-mrwakczu/SKILL.md.part' '.skill-downloads/e2e-testing-patterns-mrwakczu/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/e2e-testing-patterns-mrwakczu/SKILL.md' && test -s '.skill-downloads/e2e-testing-patterns-mrwakczu/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/e2e-testing-patterns' && cp -R '.skill-downloads/e2e-testing-patterns-mrwakczu' '.claude/skills/e2e-testing-patterns'Cursor
test -f '.skill-downloads/e2e-testing-patterns-mrwakczu/SKILL.md' && test -s '.skill-downloads/e2e-testing-patterns-mrwakczu/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/e2e-testing-patterns' && cp -R '.skill-downloads/e2e-testing-patterns-mrwakczu' '.cursor/skills/e2e-testing-patterns'Codex
test -f '.skill-downloads/e2e-testing-patterns-mrwakczu/SKILL.md' && test -s '.skill-downloads/e2e-testing-patterns-mrwakczu/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/e2e-testing-patterns' && cp -R '.skill-downloads/e2e-testing-patterns-mrwakczu' '.agents/skills/e2e-testing-patterns'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/e2e-testing-patterns-mrwakczu'openskills read 'e2e-testing-patterns-mrwakczu'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/e2e-testing-patterns-mrwakczu/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
ClickHouse Performance Comparison
Testing
Evaluate ClickHouse performance test results, check PR performance changes, compare with history, and assess whether a result is actionable.
Analyze CI Performance Reports
Testing
Analyze CI performance comparison reports for a ClickHouse PR. Cross-references master history to distinguish real regressions from flaky tests.
Santa Method
Testing
Multi-agent adversarial verification with two independent reviewers. Output is checked twice and iteratively fixed until both pass before shipping.