Check that your coding agent really ran the tests
Rohit is a security engineer who went through every time his coding agent said all tests pass over the last 30 days. Of 239 claims, 125 were backed by a passing test run after the last edit.
Done with Claude CodeModerate
What was done
Rohit is a security engineer who went through every time his coding agent said all tests pass over the last 30 days. Of 239 claims, 125 were backed by a passing test run after the last edit. 75 were stale, because the agent changed the code afterwards, and 39 had nothing behind them. He has built a free tool that reads Claude Code and Codex logs, and the post promotes it.
How to do it
- Paste the prompt into the tool, and replace the text in brackets with your own.
- Read the answer through. Do not send, delete or publish anything until you have seen it yourself.
- Check the original before you trust a figure, a name or a date.
Try it with Claude Code
Read the session logs from [period] in [log folder]. Find every time you said the tests pass, and check whether there was a passing test run after the last code change. Make a table with date, task and whether the claim held. Do not change code or logs. Show me the table before anything is changed. You are done when I can see how many claims held, were stale or had nothing behind them.
Replace text in brackets with your own.
Done when. You can see how many claims held, were stale or had nothing behind them.