Testing your agent's public output: publish, fetch logged-out, then assert
petrusenko_max · x · 2026-10-24
The author pushed their autoposter's test coverage from 84% to 100% (lines and branches) and found zero bugs — because the real bug was already live: the reply under a post carried the wrong link while every test stayed green. The fix: after every publish, the bot re-reads its own public post as a stranger would (logged out) and asserts on 6 things — correct account, no URL in the body, image attached, reply threaded properly, expected link in the reply, and no tracking params like ?sk= or source=. Test the code, then test what the world actually sees.
Related event: Developer Hits 100% Test Coverage, Still Misses Live Bug(2 posts)→
More from coding & agent
- Polylane Launches for Cloudflare: Proactive Agents Watch Workers, Merge ~8 PRs a Day — dinasaur_404 · 2026-10-24
- Factory tested Reflection's Beam pre-launch via Together AI for day-0 support — togethercompute · 2026-10-24
- Benzi: compiler-backed coding agent hits 82.4% SWE-bench Verified for under $13 — DonkeyTheKing · 2026-10-24
- Bench shows GPT-5.6/6 Luna crush multi-agent coordination while DeepSeek V4 fails — JoshPurtell · 2026-10-24
- Payman AI launches MCP server for natural-language payments and payee management — modelcontextprotocol · 2026-10-24
- Grok Bot adds secure vault so agents can log in and pay without seeing your secrets — XFreeze · 2026-10-24