Menu

Individual skill

e2e-scenario-planner

0upvotes

Plans high-value end-to-end critical user journeys with Playwright or Cypress focusing on revenue-critical flows.

skills/testing/e2e-scenario-planner/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Architect a resilient, non-flaky End-to-End (E2E) test suite using Playwright or Cypress focused on core business user journeys (authentication, checkout, workspace invitation, data export) while keeping test run times fast.

## When to Use

- Establishing an automated E2E smoke and regression suite.
- Refactoring brittle E2E tests filled with arbitrary `sleep()` calls and unstable CSS selectors.
- Prioritizing which test scenarios must run on pull requests vs nightly builds.

## What to Analyze

1. **Critical User Journeys (CUJs)**: Identify flows where a failure stops users from converting or using core features.
2. **Stable Locators**: Prioritize user-facing accessibility locators (`getByRole`, `getByLabel`, `getByText`) over brittle CSS hierarchy selectors.
Back to top