Test First Changes

Test-first procedure for every behaviour change in Noodle. Use before fixing a bug, changing how code behaves, or acting on a diagnosis made by reading the code; covers the failing test, the fix, the two runs to report, and the CI-safety constraints on tests.

pdparchitect Updated

File contents

Behaviour changes are test-first

Do not change behaviour on the strength of reading the code.

  1. Write a test that exercises the specific code and fails because of the problem.
  2. Run it and see it fail.
  3. Make the change.
  4. Run the same test and see it pass.
  5. Report both runs.

A suspected cause that no test can reproduce is still a hypothesis; say so instead of changing code.

Tests must not depend on a harness account, a model, the network or timing, so that they also pass in CI.

pdparchitect/noodle/tree/main/.agents/skills/test-first-changes commit 30a1d7fdee

Frequently asked questions

npx skillmds@latest add pdparchitect/test-first-changes