Launch HN: TesterArmy (YC P26) – Agents that test web and mobile apps

Testing has always been the part of shipping software that nobody actually enjoys. You write the feature, you ship it fast thanks to AI coding tools, and then you hit the wall: someone still has to click through the checkout flow forty times to make sure nothing broke. TesterArmy, launched on Hacker News by founders Oskar, Szymon, and Piotr, wants to hand that grind to an agent instead of a person.

The pitch is simple on paper. You describe a test case in natural language, point a CLI at your app, and TesterArmy's agent runs it end-to-end, on a schedule or triggered by a GitHub push. No selectors to maintain, no brittle scripts that break the moment a button moves three pixels to the left. When something fails, the team gets pinged in Slack or Discord instead of finding out from an angry customer.

What makes the launch post interesting isn't the framing, it's the receipts. In a few months TesterArmy went from zero to more than 30 teams running tests daily, and the founders shared specific bugs their agents caught before they reached production: a timezone bug buried in a complex booking dashboard, an agent-orchestration regression that froze a sandboxed environment, a checkout flow silently miscounting order totals, and a broken tool-calling issue that would have locked users out of their own data in an AI chat feature. These aren't hypothetical demo bugs. They're the kind of quiet, ugly regressions that hide in dashboards and chat flows precisely because they're tedious for a human tester to reproduce.

The company is also leaning hard into the idea that its own product is agent-native, meaning your coding agent, not just your engineers, can define and run tests through TesterArmy's platform. That's a deliberate bet that the near future of QA looks less like humans writing Playwright scripts and more like agents talking to agents, with a person mostly checking Slack for alerts. Whether that holds up at scale, especially for messier legacy apps with weird auth flows, is exactly the kind of thing the 69-comment HN thread is arguing about right now.