Skip to content
Skills Library
Programming · Testing

e2e-testing

/e2e-testing

Write end-to-end tests that earn their cost by covering complete user journeys against stable selectors. Use when protecting a critical path like signup or checkout across the full stack.

Repository
AI-SKILLS ↗
Licence
MIT
Last repository change
05.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Write end-to-end tests that earn their cost by covering complete user journeys against stable selectors. Use when protecting a critical path like signup or checkout across the full stack.

Original author description

Write end-to-end tests that earn their cost by covering complete user journeys against stable selectors. Use when protecting a critical path like signup or checkout across the full stack.

How it works

  1. Method
  2. Signals
  3. Boundaries
Original SKILL.md headings · 51 lines, 382 words
SKILL.md preview
---
name: e2e-testing
description: Write end-to-end tests that earn their cost by covering complete user journeys against stable selectors. Use when protecting a critical path like signup or checkout across the full stack.
---

# End-to-end testing

An end-to-end (E2E) test drives the real application the way a user does:
through the browser, across every layer, to a real result. Each one is slow,
brittle, and costly to maintain, so it has to pay rent. A suite that retests
every field validation through the UI collapses under flakiness and gets
muted. Spend E2E tests only on journeys whose failure would cost real money
or trust, and build them to survive cosmetic change.

## Method

1. **Test journeys, not pages.** One test completes a goal a user cares
   about, end to end: register, add to cart, pay, see the confirmation.
   Field-level rules and error copy belong in faster tests, not a browser
   round trip.
2. **Select by role or test id, never by styling.** Target
   `getByRole("button", {name: "Pay"})` or `data-testid="submit-order"`, not
   `.btn-primary:nth-child(3)`. Selectors tied to layout break on every
   redesign that changed no behavior.
3. **Wait on state, never on the clock.** Assert the app reached a condition,
   `await expect(page.getByText("Order placed")).toBeVisible()`, never
   `sleep(3000)`. Fixed sleeps are the primary engine of E2E flakiness and
   slowness at once.
4. **Seed data through the API, act through the UI.** Create the account and
   catalog with fast backend calls, then drive only the journey under test
   through the browser. Building prerequisites by clicking multiplies both
   runtime and failure surface.
5. **Keep the count small and the paths critical.** A handful of journeys run
   on merge beats hundreds run nightly and ignored. Rank by revenue and
   support-ticket risk, and delete any test whose failure no one would act
   on.
6. **Isolate each run's data.** Unique emails and tenant ids per run let tests
   execute in parallel without colliding, and let a failed run leave
   diagnosable state instead of poisoning the next.

## Signals

- Does each test represent a path a real user takes to a real outcome, not a
  single widget?
- Would a CSS refactor that preserves behavior leave every test green?
- When one fails, does the trace point at a broken journey rather than a
  timing accident?

## Boundaries

E2E is the narrow top of the pyramid, not where coverage lives: push edge
cases and validation down to integration-testing and unit-test-design.
Follow the team's chosen runner, Playwright, Cypress, or Selenium, over the
selector and waiting syntax shown here.

Versions

RepositoryScoreLicence
This page · Amey-Thakur/AI-SKILLS90MIT
ericrisco/rsc-harness100MIT
meteor/meteor100MIT
mthines/agent-skills100MIT
qwenlm/qwen-code100Apache-2.0
Sanit-mann/The-Insectoids100MIT
jelvodev/yaap100MIT
drvoss/everything-copilot-cli100MIT
CrowdStrike/foundry-skills100MIT

Database snapshot: 13.11.2026 · package version 17740268f045 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100proof-e2e
    Build E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests".
  • 100proof-e2e
    Build E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests".
  • 100e2e-playwright-testing
    End-to-end testing with Playwright for web applications. Use when writing E2E tests, browser automation, form submission testing, or user flow testing. Triggers on "playwright", "e2e test", "browser test", "end-to-end", "form flow testing", or test files in tests/e2e/.
  • 100e2e-testing-edho-ferdian
    End-to-end tests for critical user journeys: map flows first, use whichever browser driver is available, Page Object Model, quarantine flaky tests, keep failure artifacts. Use for "test end-to-end", "tes E2E", "uji alur pengguna", "browser test", "critical user flow".
  • 95playwright-test
    Creates Playwright browser-based end-to-end tests for Next.js pages covering complete user journeys from start to finish. Use when the user asks to "write Playwright tests", "create e2e tests", "write integration tests", "test in the browser", or mentions end-to-end testing,…
  • 100e2e-flow-tester
    Finds a web app's critical user flows (sign up, log in, checkout, password reset, creating and editing the core object, search, settings) and writes Playwright end-to-end tests that drive a real browser through them, using the project's existing Playwright or Cypress setup when…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.