skills.rest
codewizwit
codewizwitCOMMUNITY
Explore all skills by this author →
GitHub

e2e-strategy

Generates end-to-end testing strategies with Playwright or Cypress configurations and Page Object Models.

1|Updated Oct 11, 2025
Search Tags:#ci/cd#test automation#testing strategy#playwright#e2e testing#cypress#page object model
One-click install
npx skills add https://github.com/codewizwit/human-in-the-loop --skill e2e-strategy-codewizwit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-strategy
Source: https://github.com/codewizwit/human-in-the-loop/tree/main/lib/skills/e2e-strategy
Command: npx skills add https://github.com/codewizwit/human-in-the-loop --skill e2e-strategy-codewizwit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Planning end-to-end test coverage for a web application requires analyzing user flows, choosing a framework, designing maintainable test architecture, and wiring CI/CD integration, which is time-consuming to do from scratch. ## Core Features & Use Cases - Framework Detection and Recommendation: Auto-detects existing Playwright or Cypress setups from package.json, or recommends one based on the project. - Critical Flow Analysis: Scans routes, components, and authentication code to map and prioritize user journeys into P0 smoke, P1 regression, and P2 extended tiers. - Complete Strategy Document: Produces Page Object Model designs, selector strategy, test data management, CI/CD pipeline configuration, and anti-pattern guidance. - Use Case: Ask for a smoke test suite for every pull request and receive a minimal critical-path suite targeting sub-5-minute execution with example test code. ## Quick Start Analyze this application and create a comprehensive E2E testing strategy with Playwright covering all critical user flows.

Frequently Asked Questions about e2e-strategy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an E2E testing strategy for my web application?▼

Request a full application strategy and the skill scans your routes, components, and package.json to map critical user journeys. It outputs a prioritized test plan with P0 smoke, P1 regression, and P2 extended tiers plus example test code.

Playwright vs Cypress for end-to-end testing?▼

The skill can auto-detect an existing framework from your package.json or recommend one based on your project type. It supports both Playwright and Cypress and tailors configuration, selectors, and CI setup to whichever you choose.

How do I set up a smoke test suite that runs on every PR?▼

Request a smoke test scope and the skill identifies critical-path flows like login and core navigation. It produces a minimal suite targeting sub-5-minute execution with GitHub Actions workflow configuration included.

How do I prevent flaky E2E tests in CI?▼

The strategy covers wait strategies, stable data-testid selectors, authentication state reuse, and mocking external services. It explicitly flags anti-patterns like hardcoded waitForTimeout calls and shared test data between tests.

What is the Page Object Model pattern in E2E testing?▼

Page Object Models encapsulate page structure and interactions into reusable classes, keeping tests maintainable when UI changes. The skill designs the key POMs your application needs and provides TypeScript example code.

Related Skills

Explore More Software Engineering Skills→
PMDevSolutionsPMDevSolutions
7

react-testing-workflows

Configure Vitest, Playwright, Storybook, and MSW testing workflows for React TypeScript applications.

Official
Advanced
manastalukdarmanastalukdar
1

pipeline-monitor

Analyze CI/CD pipeline build success rates, flaky tests, and duration trends.

Community
Advanced
nesihaver-ILnesihaver-IL

review

Analyze code for bugs, performance issues, and security vulnerabilities.

Community
Basic
mahg-esmahg-es
3

bdd-feature

Group functional requirements into features and generate Gherkin .feature files.

Official
Advanced