e2e-testing
Skill0 starsChanged 4 months agoMITView on GitHub
Use when a user journey or cross-service behavior needs end-to-end validation.
92 other projects use a version of this.
Adopted by
Most recently taken up by
- Rojios/everything-claude-codetheir own version, first seen Nov 8, 2026
- op3616windows/skillstheir own version, first seen Nov 8, 2026
- lien0219/openxflowtheir own version, first seen Nov 8, 2026
- Lukk17/agent-standardstheir own version, first seen Nov 7, 2026
- pankaj-mahaur/Agent-Daemontheir own version, first seen Nov 6, 2026
- Cure-Consulting-Group/ProductEngineeringSkillstheir own version, first seen Nov 4, 2026
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.
InfopibeSkilleverything-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
mryeastcodeSkilleverything-claude-code-conventions
Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
Also in 8 projects that use this
tpavanipradeepSkillbun-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
niloykumarbarmanSkillagent-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
Other versions92 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 92
- affaan-m/ECC★ 246ksame name
- langflow-ai/langflow★ 156ksame name
- All-Hands-AI/OpenHands★ 93ksame name
- OpenHands/OpenHands★ 93ksame name
- pulsejet/memories★ 3.9ksame name
- xu-xiang/everything-claude-code-zh★ 1.9ksame name
- paradigmxyz/centaur★ 1.4ksame name
- etewiah/property_web_builder★ 644same name
- nodetool-ai/nodetool★ 615same name
- Opentrons/opentrons★ 532same name
82 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 repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- branch-safelySkill
- deployment-decisionsSkill
- deploySkill
- deploy-vercelSkill
- deploy-vpsSkill
- documentationSkill
- feature-testingSkill
- monitoringSkill
- orchestrateSkill
- quality-reviewSkill
- requirements-gatheringSkill
- solution-designSkill
- task-breakdownSkill
- ui-uxSkill
- unit-testingSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. 0 are common, 15 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 40 edited versions we read keep these.
15
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 12
New feature: after unit and feature tests pass, verify the complete user journey works end-to-end.
- Distinctive: line 14
Cross-service changes: when changes span multiple components, modules, or API endpoints, verify the full flow.
- Distinctive: line 18
Complete user journey: every step a real user would take from entry to goal completion.
- Distinctive: line 19
Realistic environment: run against the actual application (local dev server, test server, or staging), not mocks.
- Distinctive: line 20
Data flow: verify data persists and flows correctly through the full stack (frontend to database, API to UI, CLI to file system).
- Distinctive: line 22
Error recovery: verify the user can recover from errors in the real application (retry, go back, correct input).
- Distinctive: line 30
Every edge case (save those for unit tests.
- Distinctive: line 37
Use the project's existing E2E framework if available (for example Playwright, Cypress, Puppeteer, Selenium, httpx, curl for APIs).
- Distinctive: line 38
If no E2E framework exists, use manual simulation with exact steps and record the process.
- Distinctive: line 43
Use the actual application UI, API, or CLI as the user would.
- Distinctive: line 44
Start from a known state (clean database, fresh session, or documented starting conditions).
- Distinctive: line 46
Keep the journey focused: test the smallest meaningful complete flow, not the entire application.
- Distinctive: line 50
Start the application with its actual start command.
- Distinctive: line 51
Wait for it to be ready (check the URL responds, server logs show ready, or port is listening).
- Distinctive: line 55
Stop or clean up the application when done.
“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.
Files
End-to-End Testing
Simulate a real user interacting with the application from start to finish. E2E tests run against the actual application (browser, CLI, or API server) with real or realistic dependencies, verifying that the full user journey works.
When to write
- New feature: after unit and feature tests pass, verify the complete user journey works end-to-end.
- Bug fix: reproduce the exact user scenario that triggered the bug, confirm the fix works in the real application.
- Cross-service changes: when changes span multiple components, modules, or API endpoints, verify the full flow.
What to test
- Complete user journey: every step a real user would take from entry to goal completion.
- Realistic environment: run against the actual application (local dev server, test server, or staging), not mocks.
- Data flow: verify data persists and flows correctly through the full stack (frontend to database, API to UI, CLI to file system).
- State transitions: confirm the application state changes correctly at each step (created, submitted, processed, completed).
- Error recovery: verify the user can recover from errors in the real application (retry, go back, correct input).
- Cross-browser/cross-platform (when applicable): test at least the primary browser or platform the feature targets.
What not to test
- Unit-level logic (covered by unit tests).
- Implementation details or internal state.
- Third-party service internals.
- Every edge case (save those for unit tests; E2E focuses on critical paths).
How to set up
- Determine the actual start command for the application (for example
npm run dev,docker compose up,python manage.py runserver). - Identify the URL or port the application runs on.
- Determine any setup needed: database migration, seed data, environment variables.
- Use the project's existing E2E framework if available (for example Playwright, Cypress, Puppeteer, Selenium, httpx, curl for APIs).
- If no E2E framework exists, use manual simulation with exact steps and record the process.
How to write
- Each test should represent one complete user journey, not a single assertion.
- Use the actual application UI, API, or CLI as the user would.
- Start from a known state (clean database, fresh session, or documented starting conditions).
- Include cleanup steps to restore the application to a usable state.
- Keep the journey focused: test the smallest meaningful complete flow, not the entire application.
Running
- Start the application with its actual start command.
- Wait for it to be ready (check the URL responds, server logs show ready, or port is listening).
- Execute the user journey step by step.
- Record the actual URL, port, or CLI command used.
- Record the outcome of each step.
- Stop or clean up the application when done.
Evidence for quality
Give quality the exact start command, URL or port, step-by-step journey with actual outcomes, any failures encountered, and the cleanup command. If E2E testing is not possible (missing framework, no running application, infrastructure dependency), state exactly what prevents it and what would be needed. Do not invent E2E results. Keep the evidence concise and factual.
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.