Outcome#
You can connect a small behavior change to a regression test, run the declared checks, inspect the diff, and explain how another contributor reproduces it.
Concept#
“It works on my machine” is not research evidence. Code, dependencies, inputs, configuration, tests, and relevant versions must be identifiable.
Worked Example#
The hidden behavior check and the visible tests pass without committing the environment or generated files.
A correct example uses these decisions:
- When may you record that tests passed? After you personally ran the named test command and observed success.
- What belongs in the commit? Source, tests, and declared dependencies needed to reproduce the change.
Common Trap#
Accepting a passing command from an agent without personally running it in the intended environment.
If Blocked#
Return to the last passing baseline, inspect the first failing assertion, and reduce the problem. Do not delete tests, broaden tolerances, or install random packages merely to make the check green.
Useful references:
Understand Before Accepting AI Output#
If an agent explains the failure, independently inspect the affected source and test. Do not accept a test that only repeats the implementation or a claim that was not personally run.