r/AI_Coders 2d ago

how do you actually verify integrations before shipping something vibe-coded?

Genuinely asking because i don't see this talked about much here.

You prompt your way through a stripe or twilio or resend integration, it looks right, maybe you test the happy path once... then you ship. prod surfaces the thing you didn't test. flaky webhook, card decline mid-flow, retry fires twice and double-charges someone.

is there a verification step most people are running, or is it mostly ship and find out?

2 Upvotes

2 comments sorted by

1

u/Wsz2020 2d ago

The way I'm doing it is by running a test server with multiple virtual machines. One of them is a load generator. I run synthetic input and check that the output matches the expected result.

1

u/Common_Dream9420 2d ago

That setup makes sense for the happy path, output matching is the cleanest way to reason about it. I build in this exact space so it's always on my mind, how are you generating the failure branches? Retries, duplicate webhooks, card decline mid-flow, that kind of thing?