I Almost Shipped a Vibe-Coded Site Without Testing These 8 Flows

Description and use

A developer built a site with an AI coding tool over a weekend and discovered three bugs only after manually testing eight critical user journeys, highlighting the risk of shipping without comprehensive flow testing.

Problem

A developer built a site with an AI coding tool over a weekend and discovered three bugs only after manually testing eight critical user journeys, highlighting the risk of shipping without comprehensive flow testing.

Outcome

Manual testing of eight user journeys uncovered critical bugs that would have caused a poor user experience if shipped. The experience underscored the importance of testing high-impact flows before launch and suggested automating them with tools like CueCast.

Workflow

• Open homepage and verify load, navigation, and mobile layout
• Sign up, log in, and verify session persistence
• Test core feature submission and result handling
• Submit a form and check validation and duplicate prevention
• Upload a file and monitor processing and error handling
• Navigate between pages, test redirects and browser history
• Access protected pages while signed out and verify access control
• Test payment or subscription flow and confirm order status

Evidence

I built a site with an AI coding tool in a weekend. It loaded. The buttons worked. The main feature did what I asked. I was one click away from shipping it.

Source

First bug: my core feature submitted twice when I double-clicked the button.

Source

Second bug: after signing out, I could still open a protected page with a saved URL. Nothing on the page told me I shouldn't be there.

Source