Understand and Review AI Code

Module 3 – Design tests that challenge the draft

Page 2 of 3 · About 15 minutes per lesson, including practice.

Reduce a failure until its cause is visible

When a larger application behaves incorrectly, record the smallest input and sequence that reproduce it. Separate what you expected from what happened. Remove unrelated UI, logging, or data only in a practice copy, while preserving the failure. A small example is easier for both you and an assistant to reason about.

Change one relevant factor at a time. If you modify the threshold, input, and assertion together, you may lose the evidence for the original defect. Keep the failing test as a regression check after the repair. Record a hypothesis such as “the boundary is excluded,” then choose an experiment that could disprove it instead of merely rerunning the happy path.

Example code on Agila Forge ↗