Testing guidelines
Write tests that are trustworthy and worth maintaining. Use when adding or reviewing tests for your code. Covers what to test, the test pyramid, and the FIRST qualities.From its SKILL.md
npx -y skills add vaibhavsaxena022/skills --skill testing-guidelinesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 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.4 KB, 232 tokens by cl100k_base, as published. Nobody here has run it
Testing Guidelines
Good tests give you the confidence to change code — not busywork for coverage.
Do
- Follow the pyramid: many fast unit tests, fewer integration tests, a few E2E.
- Test behavior and outcomes through the public API.
- Keep tests independent and deterministic — no shared state, no order dependence.
- Cover the happy path + boundaries + one failure/exception path.
- Name tests for the behavior:
methodName_condition_expectedResult. - Use real collaborators where cheap; mock only slow/external ones.
Don't
- Don't test implementation details or private methods.
- Don't write flaky tests — no real clock, network, or
sleep; control time and stub I/O. - Don't assert on incidental output (log strings, field ordering).
- Don't chase a coverage % with meaningless assertions.
- Don't let one test depend on another or on run order.
FIRST
Fast · Isolated · Repeatable · Self-validating · Timely.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.