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.
2 things to look at
- 29 days oldThe repository was created 29 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 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.
Gives 0 of the 12 instructions most test skills give in 232 tokens
Counted across 964 of the 1,571 authors here whose files we hold, read 2026-08-07
- Close the browser when donein 55 of 964, across 12 files
- Wait for network idle statein 51 of 964, across 6 files
- Launch Chromium in headless modein 49 of 964, across 6 files
- Use descriptive selectors for elementsin 49 of 964, across 6 files
- Run provided scripts with help flag firstin 49 of 964, across 6 files
- Add appropriate explicit waitsin 48 of 964, across 5 files
- Use bundled scripts as black boxesin 46 of 964, across 3 files
- Do not read script source codein 46 of 964, across 3 files
- Use sync playwright for scriptsin 46 of 964, across 3 files
- Inspect dom before executing actionsin 46 of 964, across 3 files
- Run the full test suitein 37 of 964
- Write the failing test firstin 29 of 964, across 23 files
Said here and by no other author read
- mock only slow or external collaborators
- satisfy the FIRST principles
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.