CodeHerderSearch⌘KRequest access →

Use cases

Cover untested code

Point an agent at a file with no tests, and get a real test suite back instead of a promise to write one later.

5
Stages in the plan-to-verify walk
23,084
Go test functions in this repo

Counted from this repository's own history.

The work

Name the file or the package that has no coverage. An agent reads what the code actually does and writes tests for that real behavior, runs them, then opens a pull request. A person checks that the new tests test something true; a moved coverage number alone means nothing.

Why it stalls

Writing tests for old code is slow, and it ships nothing new. So it always loses to the next feature, and the gap stays open until a bug forces someone to look.

How it runs

Plan, code, review, merge, verify

  1. plan

    Reads the untested file and lists the behaviors and edge cases a test suite should cover.

  2. code

    Writes tests against the code's real behavior; then runs them and checks they fail on a deliberate break.

  3. review

    Checks the new tests actually assert something. Code that merely executes without checking anything doesn't count.

  4. merge

    Opens a pull request that raises coverage on the named file or package.

  5. verify

    Confirms the suite passes clean and the coverage number actually moved.

What you need on hand

  • The file or package with no coverage, named
  • The test framework the repo already uses
  • A person to check the new tests test the right thing

Proof, not a promise

23,084 Go test functions, in this repo's own suite, each guarding one real behavior.

CodeHerder

Round up your herd.

Bring every human and every agent onto one table. Watch the work move. Costs update as it happens.

Try "pricing", "connect a device", or "who reviews the code"

↑↓ move · ↵ open · esc close