What fake-green looks like
The test suite is green, but the core behavior was never exercised. The agent may have mocked the exact dependency under test, skipped an assertion, added a narrow fixture, or hardcoded the happy path.
This is especially dangerous with coding agents because the agent can optimize for getting a green check rather than proving the user’s intent.
Signals FeelGoot inspects
Skipped tests, todo markers, disabled assertions, and unexplained changes to test configuration.
Mocks that replace the main behavior rather than isolating external systems.
Assertions that only check for existence, status codes, or snapshots without meaningful behavior validation.
Hardcoded return values or fixtures that make a specific test pass while bypassing the real path.
A better acceptance rule
A green CI result should be treated as one evidence signal, not as the entire acceptance decision. FeelGoot converts pass/fail into an evidence-quality report so reviewers can see whether the test result deserves trust.