test-quality

Installation
SKILL.md

Test quality

A test should protect a meaningful behavior and fail when that behavior breaks. Choose tests by the defects they catch, not by their count.

Apply this guidance whether implementation already exists or is being written. It imposes no test-first sequence, mandatory TDD, or approval steps.

Choose the relevant guidance

  • Read Test value when selecting cases, choosing a test layer, or reviewing redundant coverage.
  • Read Assertions when writing expectations, names, fixtures, or snapshots.
  • Read Mocking when introducing doubles, network scenarios, or testability changes.
  • Read Reliability for async work, timers, shared state, or flaky failures.
  • Read Storybook interactions when writing or reviewing story play functions.

Apply the standard

Identify the caller-visible contract and a plausible failure. Choose the least expensive test layer that can observe it. Keep setup small, exercise real production behavior, and assert the result independently of the implementation.

Review whether the test would detect a relevant mistake: ignoring an input, returning a constant, skipping validation, or failing to update the UI. Use this as a reasoning check; mutation testing is optional, not a required tool or ritual.

Installs
15
First Seen
Nov 3, 2026