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

132 points by okwasniewski ↗ HN
Hey HN - we’re Oskar, Szymon, and Piotr, and we’re building TesterArmy (https://tester.army). TesterArmy is an agentic testing platform that runs end-to-end checks before deployment and in production. Instead of wasting hours on manual testing or maintaining static scripts, we let you specify your tests in natural language and handle everything in between. We've built the platform fully around agents. Our agent will reliably execute the tests, but your coding agent can manage everything in our platform, from defining tests in natural language to running them on your behalf.

Check out our demo video: https://www.youtube.com/watch?v=291IkUbPrlk.

We started TesterArmy because testing is still far too painful. AI coding tools have made it dramatically faster to write and ship code, but testing is still a bottleneck. Traditional E2E tests are slow to set up and expensive to maintain. Managing auth and test users is painful. Setting up staging environments is painful. Running tests reliably is painful.

We think most teams do not actually want to spend their time writing selectors or maintaining test infrastructure. They just want confidence that their core flows work. With TesterArmy, an engineer can sign up, give an agent our CLI, and let it handle creating tests and running them on schedule or on GitHub.

When something breaks, TesterArmy alerts your team through Slack or Discord.

Over the past few months, we scaled from 0 to 30+ teams using our product every day. We caught bugs in critical flows, including onboarding, checkout, and AI chat. We've got many of our customers migrating from already established competitors to us because of the quality and reliability of our agents.

Here are a few of the recent bugs that our agent found (there were quite a lot of them!):

1) Timezone bug that affected the booking flow in one of our clients' apps, the dashboard was very complex and hard to catch by a human. 2) Regression in agent orchestration that caused a sandboxed environment to be stuck on loading, thanks to TesterArmy, the team was able to resolve it before it hit production. 3) Incorrectly counting the order amount in a complex dashboard flow with checkout, thanks to TesterArmy, the team was able to resolve it before it affected revenue 4) Catching a regression in an AI chat flow that would result in a user not being able to retrieve their data due to broken tool calling.

And many more, mostly related to some incorrect API calls, 404s, unhandled errors, etc.

If this sounds useful, we would love your feedback at https://tester.army. We have a bunch of free test runs for you to try. And don’t worry, we won’t make you do sales calls, and we don’t have long onboarding or annoying setup. Our goal is an it-just-works experience.

If you're looking for an end-to-end testing solution, we'd love to hear your feedback!

47 comments

[ 0.31 ms ] story [ 72.3 ms ] thread
Does it work of mobile native applications or expo apps that have native modules?

Pricing question, the usage on the plans seems low considering in the demo you said that you have 25 tests per pr which would mean you get only 10 PRs per month on the hobby plan?

Have you been able to nail down a loop where your tool can take an open pr, guess the code path and do some testing?

We use cypress heavily for our core flows which has a similar ai prompt thing but it’s not quite ad hoc enough for smaller fixes which is where the bottleneck still comes in for us.

"Traditional E2E tests are slow to set up and expensive to maintain." I don't really understand this. If I'm already using Opus to write the code, surely it would know best what E2E tests to write to be able to verify its own output? This seems like an unnecessary external step.
(comment deleted)
Congratulations on launch, I’ve been tracking your progress since you’ve been accepted for spring batch.

Always happy to see cool products from Poland! :)

Seems interesting, but I wonder about this

> Traditional E2E tests are slow to set up and expensive to maintain.

Isn't this just using agents to create e2e tests or is there some better new approach I'm missing?

Love your approach to product. It feels like TesterArmy will become the "Vercel for testing". Refreshing stuff!
E2E tests are now quick to write due to LLMs, and are then deterministic AND cheap to run. How would this compare to the token costs of running an agent the whole time for each test? How do you make sure results stay stable regardless of the nondeterministic nature? Do customers still need to create test cases - any way to import from test case management system - based on which they could have already generate e2e tests locally?
I'm curious how your mobile testing compares to https://revyl.com

I've been experimenting with Revyl and it's really nice. I think this agent-driven testing is the future.

Curious how they frame testing on real devices: “Real devices on demand: spin up iOS simulators and Android emulators”. So those are not real/physical devices?

Physical devices for AI agents is something we at TestingBot do provide: https://testingbot.com/support/ai/mcp

not sure the pain point you mentioned resonate. with LLMs its very easy to do E2E testing. also I feel uneasy about outsourcing this part with all the security issues these days.
I wonder how does it compare to mobileboost.io, which has been used by some companies like Duolingo?
Great presentation

On a slight tangent, since we are all here...

Does anyone still believe there is a long-term future in traditional UI/UX?

It feels like a lot of attention is still going into landing pages, dashboards, and CRUD apps, while overlooking a bigger shift where fewer people will actually need to interact with those interfaces directly when the same tools can perform the underlying tasks automatically, without much UI at all.

So the bigger question is does UI/UX evolve into something else, or does a large part of it simply disappear?

I might be a bit too early. Recently I started a project and decided to skip all of that and focus to make it more friendly to AI agents and frankly so far it has been great purely from user experience but also what it delivers.

How can it perform tasks automatically? It's not magic, there has to be an UI/UX for interacting with it. Will that UI/UX be more optimized and easier to use is the question. Like would you prefer saying "close window computer" or press alt+f4 or just click on the little cross thing or equivalent. Why are we assuming all AI automagic UI/UX will be better for all tasks?
Is there a long term future in hand-crafted UI/UX? Maybe not.

Is there a future where we still have traditional UX? Absolutely.

I don't want to write a whole dissertation on this topic, so I'm just going to mention that we tried to build AI voice assistants for a decade, and while LLMs have basically solved understanding, they have not solved the UX portion.

Does it support testing on all Apple platforms (macOS, iOS, iPadOS, watchOS, tvOS, and visionOS)?
Currently, only iOS, but we can add iPadOS too!
Love using tester army to validate PRs against my preview environment. Skips the manual check much of the time and helps me ship more confidently.
Hey, I just gave it a try and ran a quick test on booking.com. It took ~3 mins for a basic test. Do you cache the test steps so that future runs are faster and they don't call LLMs for the subsequent runs?

Also your current pricing is $300 for 1K tests which means $0.3 for each test. We tried out playwright mcp and it easily consumes 1M+ tokens for a test with ~20 steps (including image input). So with this pricing are you guys default alive?

Also is there a benchmark which you ran to prove the efficacy of your testing agent? because in the current stage it is a trust me bro kinda thing.

Some digging FAST_MODEL = "google/gemini-3-flash" (fast mode primary) DEEP_MODEL = "openai/gpt-5.4" (deep mode primary) VISION_CLICK_MODEL= "openai/gpt-5.4" (the visual grounder)

fast: gemini-3-flash, falls back to gpt-5.4, 15-min run timeout, max 2 visual calls/step. deep: gpt-5.4, 15-min timeout, max 3 visual calls/step.

Why such a hard timeout, and why not latest models?

Has anyone tried to build their own version of this?

It's cool, but I'm not super excited about using some 3rd party SaaS as a critical part of my testing.