Test risky user flows yourself, not just with AI
Two hours waiting on AI test runs, then a rewrite anyway · X · @subankundesu · Oct 2026
A builder waited hours on automated AI testing and still ended up restructuring modules and rewriting the rendering layer.
The honest numbers
- Says 2 hours waiting on automated testing
As stated by the source. Not independently verified.
Lesson
Test the risky user flows yourself too. A passing AI test run isn't the same as the app working for users.
Fix prompt
Copy this into your own AI tool (Cursor, Lovable, Claude Code, Bolt…). It's general guidance written by us. Review what the AI suggests before applying it.
my AI coding tool just finished a change in my app. Before I accept it, act as a careful reviewer. 1) Summarise in plain English what changed and why, file by file. 2) Point out anything risky: auth, payments, database queries, deleted code, new dependencies, or secrets. 3) List edge cases that might break (empty data, slow network, two devices, a logged-out user). 4) Give me a 10-minute manual test plan for the real user flows, and the automated tests worth adding. Don't make further changes until I reply.
Source: X ↗