... honest answer from most of them is: "We just run it and hope." Some do a quick manual click-through. Some write a few spot checks. Some just ship and wait for users to find the bugs. We built TestSprite to solve exactly this autonomous testing that runs from your PRD and codebase but I'm curious what your actual workflow looks like before you merge. Do you have a testing step that actually works? Or is verification still ... ... part of the agentic workflow nobody has figured out? Drop your answer below genuinely want to know. Yunhao, co-founder @ TestSprite

... Comment from Cam McMaster(@cam_mcmaster1): @Bugster for taking apart my stack and reporting on bugs/tech debt. essential in a world of vibe coders Comment from Peter Shu(@peterz_shu): For frontend focused: Cursor + 21st.dev resources For backend/functionality: Cursor + testsprite MCP Pretty bare-bones :) Comment from Jochen Zehe(@jochen_zehe): Stack does not matter. At all. Most tools achieve good enough output. Thinking about tools and stack too much is a lot wasted time. I have been there. What matters ... ... that even though I have been actively building for months and have a live product, I didn't know that I even had a 'stack' ... LOL My 'stack' progressed from @Gemini and a text editor to Gemini and @vscode.dev