e2e-testing-patterns
Build reliable, fast E2E test suites with Playwright and Cypress. Critical user journey coverage, flaky test elimination, CI/CD integration.
Why use this skill?
Master end-to-end testing with OpenClaw. Learn patterns to eliminate flaky tests, speed up CI/CD pipelines, and cover critical user journeys effectively.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/wpank/e2e-testing-patternsWhat This Skill Does
The e2e-testing-patterns skill provides a robust framework for implementing reliable, maintainable, and high-speed end-to-end (E2E) testing suites using industry-standard tools like Playwright and Cypress. It focuses on testing critical user journeys rather than internal implementation details, ensuring your application remains stable even as you refactor. By emphasizing deterministic waits, independent test isolation, and the use of stable locators like data-testid, this skill helps teams eliminate flaky tests that degrade CI/CD performance. It guides you in balancing the testing pyramid, ensuring that you only write E2E tests for paths that are vital to business continuity, while relying on unit and integration tests for lower-level logic.
Installation
To integrate this skill into your environment, use the OpenClaw command-line interface:
npx clawhub@latest install e2e-testing-patterns
Ensure you have Node.js installed and the necessary browser dependencies for Playwright or Cypress configured in your CI pipeline.
Use Cases
This skill is highly recommended for:
- Creating comprehensive smoke test suites for deployments.
- Refactoring legacy codebases where you need the confidence of full-path testing.
- Debugging and eliminating flaky tests that cause inconsistent build failures.
- Establishing clear boundaries between E2E, integration, and unit testing strategies.
- Integrating browser-based automation into GitHub Actions, GitLab CI, or Jenkins pipelines.
Example Prompts
- "OpenClaw, please generate a Playwright test script for a user signup flow that captures form submission and validation errors."
- "I am struggling with flaky tests in my Cypress suite. Can you analyze my test code and suggest improvements to eliminate fixed timeouts and unreliable selectors?"
- "Help me refactor my E2E testing strategy. Which parts of my checkout flow should be covered by E2E tests versus faster component tests?"
Tips & Limitations
- Tip: Always favor
getByRoleordata-testidselectors to ensure your tests survive UI layout changes. - Tip: Use the 'Test Pyramid' mindset; if you are writing more than a few dozen E2E tests for a single feature, consider moving logic to unit tests.
- Limitation: E2E tests are inherently slower than unit tests. Do not attempt to achieve 100% code coverage with E2E; focus purely on critical business paths.
- Limitation: This skill relies on the presence of a testing framework (Playwright/Cypress). Ensure your project is already configured with one of these to see immediate benefits.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-wpank-e2e-testing-patterns": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: code-execution, file-read, file-write
Related Skills
mermaid-diagrams
Create software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams, sequence diagrams, flowcharts, ERDs, C4 architecture diagrams, state diagrams, git graphs, and other diagram types. Triggers include requests to diagram, visualize, model, map out, or show the flow of a system.
api-design-principles
Skill by wpank
auto-context
Automatically read relevant context before major actions. Loads TODO.md, roadmap.md, handoffs, task plans, and other project context files so the AI operates with full situational awareness. Use when starting a task, implementing a feature, refactoring, debugging, planning, or resuming a session.
clear-writing
Write clear, concise prose for humans — documentation, READMEs, API docs, commit messages, error messages, UI text, reports, and explanations. Combines Strunk's rules for clearer prose with technical documentation patterns, structure templates, and review checklists.
track-performance
Track the performance of Uniswap LP positions over time — check which positions need attention, are out of range, or have uncollected fees. Use when the user asks how their positions are doing.