Upload a build
Point the CLI at the .app or .apk your CI already produces and it lands in the dashboard.
[02] Upload a build, run a test
Upload a build,
run a test
Upload the Simulator .app or .apk your build produces. Agents install it on cloud devices and click through your flows.
Upload, then run
Your coding agent uploads the .apk through the CLI, runs the test you name and reads back the verdict.
Choose the device
Runs on iPhone by default, or on iPad in landscape or an Android emulator when you choose.
iOS result
Every iOS run lands in Results with its status, platform and environment, next to your web tests.
Android result
Android runs from the same test show up as their own row with a Passed or Failed verdict.
Put your build in front of the agents
Upload the Simulator .app or .apk you already build and watch agents click through it.
[03] iOS and Android from one test +
iOS and Android from one test
Write the flow once in plain language. Run it on an iPhone Simulator and an Android emulator, and read both results side by side in the same Results table.
One test,
both platforms
The same plain-language flow runs on an iPhone Simulator and an Android emulator, and each platform gets its own row and verdict in Results.
Manual or pull request
Start runs from the dashboard, or have CI upload each build and test it on the pull request.
Test Accounts
Agents sign in with the Test Accounts you save, and a saved inbox reads OTP codes for them.
Results in Slack
A failed run posts the test, the failing step and what the agent saw, with a link to the run.
Both platforms
Filter Results by platform, or leave it on All platforms and read iOS and Android rows together.
[04] Explore the platform +
Run at every step of shipping
The same tests run on every pull request, from your CI job, on a schedule against Production, or by hand. Every run lands in one Results table.
[04] Proof
Mobile teams that stopped
testing by hand
In sixteen years of building mobile apps, TesterArmy is the first tool that actually does what I always expected AI-powered testing to do. You're onto something.
Edwin Huertas
CEO, Shockoe
FAQ
Frequently asked questions
What differs between iOS and Android runs?
iOS runs use a Simulator .app on a cloud iOS Simulator. Android runs use an .apk on a cloud Android emulator. The same plain-language test can run on both, with a separate result and recording for each platform.
How does CI integration work?
Upload the build your CI produces with the TesterArmy CLI, then run your saved tests against it. TesterArmy installs the app, runs the test and returns the report. You can connect these runs to your pull request workflow.
Can it test in-app purchases and subscriptions?
Agents can test paywalls, plan selection, upgrade and downgrade screens, restore-purchase flows and post-purchase navigation. Native purchase sheets depend on your app's simulator or emulator sandbox configuration.
Can it test Apple Pay checkout?
Yes, for native iOS apps configured for Simulator testing. Agents can inspect the payment sheet, authorize the simulated payment and follow the confirmation flow. Simulator authorization uses a dummy token rather than processing a real payment.
How do I automate mobile app testing without QA engineers?
Upload a build and describe a flow in plain language. Save it as a test, run it on the selected platform and inspect the report. Anyone on the team can add steps without setting up a test framework or device lab.
Does it work with React Native and Expo?
Yes. TesterArmy installs the compiled app, so React Native and Expo builds use the same test workflow as native apps. Provide an iOS Simulator .app or Android .apk.
Can it test login flows with OAuth and OTP codes?
Yes. Configure Test Accounts for your login flow. Agents can sign in with saved credentials and read verification codes or magic links from an inbox. Your OAuth provider and app must support the selected Simulator or emulator environment.
How is this different from Detox or Maestro?
You describe the flow in plain language instead of writing and maintaining a test script. TesterArmy manages cloud execution and collects the step results, recording and screenshots from each run.
