Webapp testing
Skill kimtth/agent-skill-100-lines-or-less/skills/webapp-testing
Use when: test a web app across unit, integration, and end-to-end layers with the right balance.From its SKILL.md
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill webapp-testingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 228 tokens by cl100k_base, as published. Nobody here has run it
Goal: cover behavior at the cheapest layer that proves it.
Use for:
- adding tests to a web app or feature
- deciding what to unit test vs. integration vs. e2e
- replacing brittle tests that break on refactors
Workflow:
- Identify the behavior and its user-visible contract.
- Choose the lowest layer that can verify it honestly.
- Unit test pure logic; integration test wiring; e2e the critical paths.
- Set up real dependencies where feasible; mock only true boundaries.
- Make tests deterministic: control time, network, and data.
- Run, confirm meaningful failure, then keep green.
Layer guidance:
- unit: pure functions, reducers, validation
- integration: components with real children, API handlers with a real db
- e2e: signup, checkout, and other revenue-critical flows
Rules:
- test behavior, not implementation detail
- do not mock what you are trying to verify
- keep e2e few and high-value; they are slow and flaky-prone
- a test that never fails has no value
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.