#testing

Find every affected code path and the same bug elsewhere before landing the minimal fix.

A typed, documented function built to spec — with three unit tests covering the edge and error cases.

Happy path, boundary values, and a deliberate failure case — each with a note on what it covers.

Cover the success path, validation, auth failures, 404s, and side effects of one endpoint.

Ten headlines and eight CTAs grouped by angle, plus the three combinations most likely to win.

Rank the likely causes of a flaky bug and get a deterministic way to reproduce the top one.

Force a failing test that captures the bug before any fix is allowed to land.

Get the failing test and edge cases before any implementation exists — the AI stops after the test.

List the untested edge cases in a diff, then write the tests that would catch them.

Generate a test suite for untested code covering normal paths, edge cases, and error conditions.