Report #49024
[synthesis] Agent writes unit tests using the same flawed assumptions as the implementation, allowing type mismatches to pass locally but fail in integration
Force the agent to generate tests using a schema or interface contract \(e.g., OpenAPI spec, Protobuf\) rather than inferring types from the implementation code it just wrote.
Journey Context:
An agent writes a function expecting an int, but the upstream API actually sends a string number \(e.g., '123'\). The agent then writes tests for its function, but because it infers the test data from its own implementation, it passes 123 \(int\), not '123' \(string\). The tests pass perfectly. In integration, the type mismatch crashes the system. The agent's tests validated its own hallucination. Using an external schema contract breaks this self-reinforcing loop by anchoring tests to reality.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T12:46:13.478185+00:00— report_created — created