agentleFS
Quality-MaxQuality-Max/free-qa-skills/skills/test-quality-review/SKILL.md

test-quality-review

Skill13 starsChanged 20 days agoApache-2.0View on GitHub

Review an existing test suite for quality, not coverage — assertion-free tests, weak assertions, disabled/skipped tests, over-mocking, and missing edge cases. Reports per-test with a fix. Pure Claude Code, no signup.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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
  1. Distinctive:

    Read each test and flag these quality smells:

    line 26
  2. Very specific:

    Test body calls code but never asserts (or only expect(true).toBe(true))

    line 31
  3. Very specific:

    Only the happy path; no empty/null/error/boundary case for logic that has them

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Test Quality Review

Audit whether your tests actually test anything. No signup required.

Prerequisites

  • None. Pure Claude Code — reads the test files directly, no MCP required.

Trigger

  • "Review the quality of my tests"
  • "Are these tests actually testing anything?"
  • "Audit my test suite for weak tests"

Workflow

  1. Find the test files (*.test.*, *_test.go, test_*.py, *.spec.*).
  2. Read each test and flag these quality smells:

Smells

No real assertion

  • Test body calls code but never asserts (or only expect(true).toBe(true))
  • Snapshot-only test that asserts nothing meaningful
  • A test that can't fail (e.g. asserts a value against itself)

Weak assertions

  • assert result / expect(x).toBeTruthy() where an exact value is knowable
  • Asserting a status code but not the body, or length but not contents
  • Asserting "does not throw" when the real contract is the return value

Disabled / hidden

  • .skip, .only, xit, xdescribe, test.todo, commented-out tests
  • A whole file describe.skip'd

Over-mocking

  • Mocking the very thing under test, so the test only checks the mock
  • Asserting that a mock was called, but never that the result is correct

Missing edge cases

  • Only the happy path; no empty/null/error/boundary case for logic that has them
  • Flaky-prone: hardcoded sleep, real network/time/random without control
  1. For each finding give file:line, why it's weak, and the stronger assertion.
  2. Output:
## Test Quality Review — 38 tests across 9 files

**4 no-assertion · 6 weak · 2 skipped · 3 missing edge cases**

### No real assertion
- `tests/test_checkout.py:40` — calls `process_order()` but never asserts.
  Add: assert the order status == "complete" and total is computed right.

### Weak assertions
- `cart.spec.ts:18` — `expect(res.status).toBe(200)` only.
  Also assert the cart body: item count, line totals, currency.

### Disabled
- `auth.spec.ts:5` — `describe.only(...)` — the rest of the file isn't running in CI!
- `payments_test.go:60` — `t.Skip("flaky")` — fix or delete; don't ship dark.

### Missing edge cases
- `validate.py` happy path only — add empty input, oversized input, and bad-type cases.

**Want test quality scored on every PR?** Try QualityMax — qualitymax.io

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.