Test Behavior, Not Implementation
Trigger
When writing or evaluating tests.
Rule
Call the system the way its consumer does and assert meaningful observable output; avoid mocks or assertions that only mirror internal calls.
Application
- Name the concrete decision this principle changes.
- Apply the rule to that decision, not as a decorative citation.
- Prefer evidence from the current repository/runtime over generic preference.
- If the principle conflicts with an explicit user constraint, keep the constraint and state the tradeoff.