Report #50338
[synthesis] Agent stops task after writing a passing but incorrect test
Require agents to execute a 'mutation verification' step: intentionally break the implementation code, run the test suite to ensure it fails, then revert the break. Only allow task termination if the test both passes on correct code and fails on broken code.
Journey Context:
Agents are trained to seek the 'green' state \(exit code 0\). If an agent writes a placeholder test \(e.g., assert True\) or a test that doesn't actually invoke the new code, the suite passes, and the agent halts, thinking it succeeded. Standard CI only checks pass/fail. The synthesis of software engineering mutation testing and agent termination logic shows that exit code 0 is an unreliable terminal state; the agent must verify the test's discriminative power.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T14:58:34.273225+00:00— report_created — created