agentleFS
Sign inStart free
malinskibeniaminmalinskibeniamin/skills/e2e-testing/SKILL.md

e2e-testing

Skill4 starsChanged 10 days agoMITView on GitHub

Use when writing or fixing Playwright E2E specs, fixtures, browser tests, or flakes.

92 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use everything-claude-code, investor-materials and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • InfopibeSkill

    everything-claude-code

    Also in 10 projects that use this

  • InfopibeSkill

    investor-materials

    Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.

    Also in 28 projects that use this

  • mryeastcodeSkill

    everything-claude-code-conventions

    Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

    Also in 8 projects that use this

  • tpavanipradeepSkill

    bun-runtime

    Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.

    Also in 18 projects that use this

  • niloykumarbarmanSkill

    agent-sort

    Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

    Also in 8 projects that use this

  • niloykumarbarmanSkill

    product-capability

    Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints, invariants, interfaces, and unresolved decisions before multi-service work starts. Use when the user needs an ECC-native PRD-to-SRS lane instead of vague planning prose.

    Also in 9 projects that use this

  • +1 more from Infopibe

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 6 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 40 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run /read-the-damn-docs before choosing current Playwright, Testcontainers, axe-core, or browser APIs.

    line 11
  2. Very specific:

    Put E2E tests in e2e/*.spec.ts.

    line 16
  3. Very specific:

    Test IDs use {feature}-{element}, optional index, or state.

    line 18
  4. Distinctive:

    Run axe on every page, but automated accessibility covers only a subset.

    line 24
  5. Very specific:

    Wait for causes, never durations.

    line 33
  6. Distinctive:

    Test navigation races by delaying A, starting A, navigating to B, then proving B's state and effects while A stays absent.

    line 36
  7. Very specific:

    Never use force: true; fix the obstruction a user would hit.

    line 40
  8. Distinctive:

    Keep ephemeral UI visible in test mode, but assert lasting side effects rather than toast text.

    line 43
  9. Distinctive:

    Run clipboard and permission-specific specs in Chromium.

    line 44
  10. Distinctive:

    Use one CI retry only as a stopgap and zero as the goal.

    line 46
  11. Distinctive:

    Delete render-only specs; each journey exercises a user-caused side effect.

    line 47

“Common” is measured: kept by at least 6 in 10 of the 40 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

E2E Testing

Run /read-the-damn-docs before choosing current Playwright, Testcontainers, axe-core, or browser APIs. Setup belongs in SETUP.md.

Conventions

  • Put E2E tests in e2e/*.spec.ts; name files by feature.
  • Select with getByRole > getByLabel > getByText > getByTestId > CSS.
  • Test IDs use {feature}-{element}, optional index, or state.
  • The route sibling hook runs nearby browser/integration tests after route edits.
  • The structural refactor hook requires a test for new pages or extracted components.

Accessibility and browsers

Run axe on every page, but automated accessibility covers only a subset. An axe-only pass does not prove keyboard order, focus, names, zoom, or assistive-technology behavior.

On PRs, run the full suite in Chromium. Tag critical journeys and credible engine risks @cross-browser; run those in Firefox and WebKit. Reserve the full browser matrix for a nightly lane or release gate. Emulation cannot prove every branded browser or physical device.

Determinism

  • Wait for causes, never durations. Register response/request/render promises before the action. After waitForURL, assert a destination landmark. Ban waitForTimeout and expect.soft inside toPass.
  • Test navigation races by delaying A, starting A, navigating to B, then proving B's state and effects while A stays absent.
  • Prove debounce deadlines and cancellation with fake timers below E2E; E2E asserts visible outcomes without sleeping.
  • Never use force: true; fix the obstruction a user would hit.
  • Match RPC routes by Service/Method, never a versioned prefix.
  • Wrap logical actions in test.step() so CI identifies the failed step.
  • Keep ephemeral UI visible in test mode, but assert lasting side effects rather than toast text.
  • Run clipboard and permission-specific specs in Chromium; cover equivalent outcomes elsewhere.
  • Buffer backend/container logs through teardown and capture startup failures. Redact secrets.
  • Use one CI retry only as a stopgap and zero as the goal. Prefer compact local reporters.
  • Delete render-only specs; each journey exercises a user-caused side effect.

Generated and long-lived exploration

For combinatorial customer contracts that cannot be proved cheaper, use narrow generated action sequences or a stateful property. Follow PROPERTY-BASED-TESTING.md: keep an independent oracle and replay seed, then convert real findings to deterministic regressions. This complements fixed journeys, cross-browser checks, accessibility, visual review, and dogfood.

For listener, DOM, timer, subscription, or heap growth within one browser context, use SOAK-TESTING.md. Isolated E2E tests cannot prove resource lifetime.

Evidence and tools

Monitor bun run test:e2e; react to failures before completion.

NeedTool
CI/test suitePlaywright
Selector or AI inspectionagent-browser snapshot
Visual smoke evidenceagent-browser screenshot --annotate
Interactive debuggingPlaywright UI mode

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free