READER EDITION / ISSUE 001 / Revised 2026-11-15
Creative Agentic Computing
CodeFarmer / Issue 001
DEBUGGING DESK

Follow the test.
Find the assumption.

A test can make the wrong assumption too. Our browser test pressed Grow in Digital Garden, then checked a counter using an assertion: an expected condition. The program advanced, but the check demanded a generation number above one. An earlier restore had reset that number to zero.

The test had carried an assumption from an earlier part of the session. The correction was to record the generation immediately before pressing Grow and then check that the counter increased. The correction belonged in the test; the program kept its intended behavior.

Write down the sequence

Write the starting state, action, expected result and observed result. “Restore a garden, press Grow, wait for one tick, then inspect generation” gives an investigation a starting point. A tick here is one timed simulation update; the counter should increase from its value just before Grow.

Test the behavior you care about

The sequencer check uses the same note-making code as the supplied program. It renders sound into an offline audio buffer, a block of audio samples held in memory. Finding a non-zero signal shows that code generated sound data; a separate listening review judges how it sounds.

A test is a small argument about a program. When it fails, inspect both sides of that argument.