webapp-testing
Skill0 starsChanged 3 months agoMITView on GitHub
Write comprehensive tests, run test suites, analyze failures, and fix tests while maintaining test integrity. Covers unit testing, integration testing, E2E testing with Playwright, and test-driven development. Use after code changes to ensure coverage or when creating new test suites.
196 other projects use a version of this.
Adopted by
Most recently taken up by
- rvdbreemen/OTGW-firmwaretheir own version, first seen Nov 8, 2026
- BrightGold70/skillstheir own version, first seen Nov 8, 2026
- DnsQueen/orcinus-skillstheir own version, first seen Nov 8, 2026
- Liang-MH/skillstheir own version, first seen Nov 8, 2026
- smart-coder-labs/nexus-mindtheir own version, first seen Nov 8, 2026
- codewhale-hq/codewhale-plugin-marketplacetheir own version, first seen Nov 8, 2026
Used with
Projects with it also use academy-guide, skill-share 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.
AnthropicSkillacademy-guide
Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.
Also in 8 projects that use this
ArogyaReddySkillskill-share
A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.
Also in 23 projects that use this
SKB3002Skillintelligent-routing
Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.
Also in 5 projects that use this
ArogyaReddySkillraffle-winner-picker
Picks random winners from lists, spreadsheets, or Google Sheets for giveaways, raffles, and contests. Ensures fair, unbiased selection with transparency.
Also in 26 projects that use this
zephyrwang6Skilltopic-collector
AI热点采集工具。从Twitter/X、Product Hunt、Reddit、Hacker News、博客等采集AI相关热点内容。当用户说"开始今日选题"、"采集热点"、"看看今天有什么新闻"、"今日AI热点"时触发。聚焦领域:Vibe Coding、Claude Skill、AI知识管理、AI模型更新、AI新产品、海外热点。
Also in 4 projects that use this
zephyrwang6Skilldeepl
Übersetzt Texte, Dokumente und XLIFF-Dateien via DeepL API. Verwende für Übersetzungen mit /deepl translate, /deepl file oder /deepl xliff.
Also in 4 projects that use this
- +4 more from zephyrwang6
- +1 more from ArogyaReddy
Other versions196 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 196
- anthropics/skills★ 189ksame name
- ComposioHQ/awesome-claude-skills★ 75ksame name
- github/awesome-copilot★ 41ksame name
- ComposioHQ/awesome-codex-skills★ 17ksame name
- composio-community/awesome-codex-skills★ 16ksame name
- vudovn/ag-kit★ 8.2ksame name
- vudovn/antigravity-kit★ 8.2ksame name
- Galaxy-Dawn/claude-scholar★ 5.9ksame name
- microsoft/FluidFramework★ 4.9ksame name
- Prat011/awesome-llm-skills★ 1.7ksame name
186 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 repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- a11y-auditSkill
- ai-engineerSkill
- api-clientSkill
- changelog-enforcerSkill
- code-cleanup-guardianSkill
- code-reviewerSkill
- contract-testSkill
- db-migrateSkill
- dep-auditSkill
- devops-automatorSkill
- env-configSkill
- error-observabilitySkill
- frontend-designSkill
- git-commit-helperSkill
- github-issues-managerSkill
- git-issue-syncSkill
- git-protocolSkill
- handoffSkill
- incident-responseSkill
- init-projectSkill
- karpathy-guidelinesSkill
- market-researcherSkill
- parallel-agent-git-isolationSkill
- product-strategistSkill
- pr-workflowSkill
- rapid-builderSkill
- release-managerSkill
- resumeSkill
- scrutinizeSkill
- shadcn-uiSkill
- skill-builderSkill
- sprint-plannerSkill
- state-machine-diagramsSkill
- state-managementSkill
- surveySkill
- system-architectSkill
- tech-docsSkill
- unstuckSkill
- ux-design-systemSkill
- ux-researchSkill
- web-dev-fundamentalsSkill
- workflow-optimizerSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 190 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Test behavior, not implementation
- Distinctive: line 22
Create test data factories
- Very specific: line 49
Run tests: npm test or pytest
- Distinctive: line 55
Don't: use flaky selectors that change
- Very specific: line 56
Do use descriptive selectors: text=, role=, IDs
- Distinctive: line 59
All tests passing before merge
- Distinctive: line 61
No skipped tests without justification
“Common” is measured: kept by at least 6 in 10 of the 190 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
Web Application Testing
Comprehensive test automation covering unit, integration, and E2E testing.
Test Types
| Type | Scope | Speed | Use For |
| Unit | Single function | <100ms | Logic, utilities |
| Integration | Component interaction | <1s | APIs, services |
| E2E | Full user journey | <30s | Critical paths |
Best Practices
- Test behavior, not implementation
- One assertion per test for clarity
- AAA pattern: Arrange, Act, Assert
- Create test data factories
- Mock external dependencies appropriately
Playwright E2E Testing
Decision Tree
Static HTML? → Read HTML for selectors → Write script
Dynamic? → Server running? → No → Start it in the background (e.g. `npm run dev &`) and wait for its port
→ Yes → Navigate → wait for the content under test → Screenshot → Identify selectors → ExecuteTemplate
from playwright.sync_api import sync_playwright
with sync_playwright() as p:
browser = p.chromium.launch(headless=True)
page = browser.new_page()
page.goto('http://localhost:5173')
page.get_by_role('main').wait_for() # wait on the content under test, not 'networkidle'
# ... test logic
browser.close()TDD Workflow
- Identify affected test files after code changes
- Run tests:
npm testorpytest - On failure: Parse errors, distinguish legitimate failure vs outdated expectations vs environment
- Fix: Preserve original intent, update expectations only for legitimate changes, never weaken tests to pass
Common Pitfalls
- Don't inspect the DOM of a dynamic app before the content you need has rendered. Wait on that element (
expect(locator).to_be_visible()), not onnetworkidle, which Playwright's docs discourage for tests - Don't use flaky selectors that change
- Do use descriptive selectors:
text=,role=, IDs
Quality Gates
- All tests passing before merge
- Coverage maintained or improved
- No skipped tests without justification
- E2E tests cover critical user journeys
- Tests run in <10 minutes total
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.

