Home / Lessons / Judge the result / 22 of 27
No feature, no bug
The error went away because the feature went away.
- A screen with one broken part. One check is failing.
- The agent removes the screen.
- Every check passes. None of them asked whether anyone can still use it.
- So a new check asks the real question, down to what the user sees.
The fix traced the feature through every layer: definition, import, render, state, user action, backend, saving, visible result. The test target became what the user is meant to be able to do, not the absence of an error.
This is why passing checks cannot define correct by themselves. A check can pass after the product has stopped doing what it is for.
How I do it
Tests now assert the intended behaviour, layer by layer, to the result the user sees.
The rule
Test for the thing that should happen. Silence is not a result.
Rule 22. Test for the thing that should happen. Silence is not a result. (No feature, no bug, https://chiefofagents.si/one-page#rule-22)
The skill I use for this: /verification-before-completion. Made by Jesse Vincent.
Read next
The ideas behind it
This lesson as plain text, for your agent. Or all 27 on one page.