#testing

A test that passes for the wrong reason leads to a practical way to assess how a team scopes, verifies, explains, fixes and hands over an agent’s work.

When the same accepted correction returns, test whether it belongs in a linter, type, test, example, repository rule, checklist, or architecture decision.

Separate test creation from implementation, verify the expected failure, and give automated TDD retries an explicit exit path.