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'm usually asking Claude to write unit tests and integration tests after it wrote some code under my supervision - therefore trying to always stay covered :)
ApyHub : The All in one API Platform
@sk_uxpin thats a good one. And do you write your own test cases or claude does?
For testing, creating good evals is critical! Both offline & online eval dashboards. Online evals run with every user so you can see performance in real time. Offline evals are created to pressure test before launch, so that users don't break things to begin with. This Lenny's podcast episode on evals was super useful for me: youtube.com/watch?v=BsWxPI9UM4c
I still test the important flows myself especially when APIs or user data are involved. For small internal tools I move faster but I don't fully trust agent output w/o checking it. Do you use a separate agent just for breaking/testing the app?
i think experienced vibe coders test aggressively because they know AI can be surprisingly right and surprisingly wrong at the same time. I always verify functionality before calling anything finished.