e2e-test
Skill1 starsChanged 6 days agoMITView on GitHub
Writes end-to-end tests for a user journey through the running app, Playwright preferred. Use when user requests e2e, end-to-end, Playwright, or Cypress tests.
28 other projects use a version of this.
Adopted by
Most recently taken up by
- muxy-app/muxytheir own version, first seen Nov 15, 2026
- eyssette/js-templatetheir own version, first seen Nov 1, 2026
- korya/swd-skillstheir own version, first seen Nov 1, 2026
- liaohch3/claude-taptheir own version, first seen Oct 25, 2026
- maximhq/bifrosttheir own version, first seen Oct 20, 2026
- DongDuong2001/pudo-code-systemtheir own version, first seen Oct 13, 2026
Used with
Projects with it also use design-md, changelog and 5 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.
klauswgSkilldesign-md
Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files
Also in 3 projects that use this
HashiCorpSkillchangelog
Add a `.changelog/<PR_NUMBER>.txt` entry for a GitHub Pull Request, commit, and push.
Also in 3 projects that use this
MicrosoftSkillplaywright-cli
Automate browser interactions, test web pages and work with Playwright tests.
Also in 3 projects that use this
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
Also in 3 projects that use this
GoogleSkillimprove-codebase-architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Also in 3 projects that use this
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 4 projects that use this
- +1 more from google
Other versions28 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 28
- metabase/metabase★ 50ksame name
- dataelement/bisheng★ 12ksame name
- maximhq/bifrost★ 9.6ksame name
- liaohch3/claude-tap★ 3.3ksame name
- muxy-app/muxy★ 2.4ksame name
- Nexus-Mods/Vortex★ 1.6ksame name
- nwiizo/tfmcp★ 373same name
- divinevideo/divine-mobile★ 265same name
- rabble/nostrvine★ 265same name
- coleam00/link-in-bio-page-builder★ 229same name
18 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- behavioural-testSkill
- breakdownSkill
- commitSkill
- find-rcSkill
- rubberduckSkill
- specSkill
- terseSkill
- unit-testSkill
- behavioural-testSkill
- breakdownSkill
- behavioural-testSkill
- breakdownSkill
- commitSkill
- e2e-testSkill
- find-rcSkill
- rubberduckSkill
- specSkill
- terseSkill
- unit-testSkill
- commitSkill
- e2e-testSkill
- find-rcSkill
- mobile-web-fixesSkill
- rubberduckSkill
- specSkill
- terseSkill
- unit-testSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Read existing e2e config, nearest e2e tests, routes and pages on journey.
- Distinctive: line 24
No fixed sleeps; rely on auto-waiting and web-first assertions.
- Distinctive: line 25
No conditionals on page state.
- Distinctive: line 27
Do not change production code to make tests pass.
- Distinctive: line 28
Start app with project's command.
- Distinctive: line 29
Run project lint and type checks on test file.
“Common” is measured: kept by at least 6 in 10 of the 24 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.
Files
E2E test
Short evidence, no emojis. No target journey named: reply "Please mention the user journey that you want me to help you write the e2e tests for." and stop.
Sphere: full user journey through running app, browser to backend. Branch and boundary detail belongs in unit-test; one scope with mocked lowest layer in behavioural-test. Case fits another sphere: say so, do not write it here. Only critical journeys here.
Tool: Playwright preferred. Cypress only when project already uses it. Neither installed: ask user, add no dependency without approval.
- Read existing e2e config, nearest e2e tests, routes and pages on journey. Reuse project's base URL, fixtures, auth setup, page objects, file naming, test location. Find app start command and test environment; state both.
- List cases: journey start, each step, end state, one critical failure path. Skip variations coverable in lower spheres; name them.
- Write tests. Rules:
- Arrange-Act-Assert: three blocks in that order, blank line between. Label with
// Arrange,// Act,// Assertonly if project tests already do. Arrange seeds data and signs in; Act is one journey of user steps; Assert checks end state. - One journey per test. Several asserts allowed only when they describe same end state.
- Name states journey, condition, expected result.
- Mock nothing inside app. Third-party service only when no test environment exists; state it.
- Drive as user: locate by role, label, text; test ids last resort. No CSS/XPath tied to markup. No direct state or storage edits in Act.
- Assert user-visible end state: URL, visible content, persisted result after reload where relevant.
- Independent tests: each creates and cleans own data, unique per run. No order dependence. Auth via project's stored-state or fixture, not repeated UI login, unless login is journey.
- No fixed sleeps; rely on auto-waiting and web-first assertions.
- No conditionals on page state. Flaky test: find cause, never add retries to hide it.
- Credentials from environment or project fixtures. Never hardcode or commit secrets.
- Do not change production code to make tests pass. Suspected bug: keep failing test, report to user, ask before fixing.
- Arrange-Act-Assert: three blocks in that order, blank line between. Label with
- Start app with project's command. Never target production without authorisation. Run new tests alone; show invocation + result. Failure: read trace/screenshot, decide whether test or app wrong, fix test only when test wrong. Rerun until green; run 3 times to check flakiness.
- Run project lint and type checks on test file; fix every error. Run full e2e suite when feasible; else state not run.
- Repeat 4-5 after each edit. Report journeys covered, cases skipped with reason, environment and browsers used, suspected bugs, commands run. Never claim passing without run output.
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
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.

