Do Vibe coders actually test things?
If the agent writes the code… who’s actually testing it?
Do you still go through edge cases and user scenarios manually, or are you also delegating “please break my app” to another agent now?
Has testing become more systematic and automated in your workflow, or you just moving faster with fewer guardrails (and let users break things) ?
Also, do you test any of your endpoints?
Preparing for a launch soon and looking to connect with people that love breaking APIs and automate flows.
you can follow to stay in touch with the launch. Also looking to connect with folks that launch cool stuff in the dev productivity space, AI and tolling overall. With my team we often do reviews of our favorite new products (from product hunt and from other places) internally so happy to check out yours!
Linkedin: https://www.linkedin.com/in/nikolasdimitroulakis/
Nikolas
Replies
I believe that testing has to be done mostly manually
the honest answer is the test bar moved. the new test is. does the customer signoff hold up. does the receipt the user published verify. does the peer signature stand. if you shipped a vibecoded thing and got real signatures on it, you tested the thing the market actually cared about. building TAM Network on exactly this premise.
I let AI write the code, but I still don't trust it enough to test itself 😄
Real users are still the best QA team on the planet.
I vibe coded cepho, and i can promiss you, i have never in my life, tested anything more then cepho has been tested.
I am building this from the opposite direction with Project Telos: not another generator, but the receipt layer after an agent run. The test I care about is whether a reviewer can replay the important facts later: original task, files inspected, side effects proposed, approvals granted, commands run, diffs created, tests/evals run, and claims the agent could not verify.
For vibe-coded work, the missing primitive feels less like "another test agent" and more like a durable verdict: what passed, what failed, what changed since the last run, and what still needs a human to check.
Yes certainly. Test and test aggressively! vibe-coded apps are not perfect. They have a lot of bugs, UX issues, security and functional gaps. You should also put yourself in the user's shoes and I am sure you will find a lot of things to fix. While Claude, for example, offers audits for security checks, there are gaps and you need a good pair of eyes to find and fix them, especially race conditions that open up security holes in your app.
most of the replies here are about ui and flows, but you slipped in the real one at the end: endpoints. clicking through the ui only tests the paths the ui offers, while the api will take a request the ui would never send, someone else's id in the params or a field the form doesn't expose. the agent writes the route so the happy path works and stubs the auth check to match. what caught the most for me was hitting my own endpoints with a second account's token and seeing what came back.