Test groups
One row per test holds its iOS and Android runs, expanded with a click.
[02] One test, two platforms
One test,
two platforms
Write the flow once in plain language. It runs on the iOS build and the Android build, grouped under one test.
Grouped by test, split by platform
Each test holds its iOS and Android runs with their own status and duration, on the same page as every other run.
iOS run
The iOS Simulator build runs the same steps and reports its own status and duration.
Android run
The Android APK runs the same flow, so a failure on one platform is visible at once.
React Native and Expo
Works with bare React Native and Expo projects, using the release build your pipeline already produces.
Test both builds from one flow
Upload the iOS and Android builds and read both results in one place.
[03] Tested on the release build +
Tested on the release build
Upload the iOS Simulator app and the Android APK your build already produces with ta upload-app. Agents test the built app, JavaScript bundle included, the way a user would.
iOS Simulator
build
Upload the .app your iOS build produces and agents drive it on the Simulator like a user.
Android release build
Upload the release APK from your Gradle build and agents test it on Android.
The same checkout flow
Agents tap through the app as a shopper would, on either platform, with no test scripts.
Platform-specific failures
A flow that passes on iOS and fails on Android shows up as its own row.
Upload with the CLI
One ta upload-app command sends the builds your pipeline already produces.
[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 is automated React Native app testing?
Agents install your compiled React Native app and execute a user flow on a cloud iOS Simulator or Android emulator. You describe steps in plain language and receive a result, recording and screenshots for each run.
Do I have to add testID props to my components?
No. Agents interact with the app's visible interface, so you can describe what a user should do without adding testID props or maintaining a set of selectors.
Can it test OTA updates from EAS Update?
Yes, when the uploaded release build can load the update you want to test. Configure the update channel or provide the relevant deep link, then run the same saved tests against that build.
How is this different from Maestro?
Maestro runs flows you write and maintain in its test format. With TesterArmy, you describe the journey in plain language and the service manages cloud execution and collects the recording, screenshots and step results.
Do I need Detox, Appium, or Maestro?
No. Upload a release build with its JavaScript bundle and describe the flow in plain language. TesterArmy runs it without adding another test framework to your React Native project.
Why does a run end BLOCKED with MOBILE_RELEASE_BUILD_REQUIRED?
The uploaded app expects a development server or Metro bundle that is unavailable on the cloud device. Build a self-contained release app with its JavaScript bundle included, upload it and rerun the test.
Does it work with Expo?
Yes. Use an Expo build for the iOS Simulator or an Android APK with the JavaScript bundle included. The Expo app testing page and EAS integration docs cover the build and upload workflow.
How do I upload my iOS and Android builds?
Use ta upload-app with the path to your iOS Simulator .app or Android .apk, or upload the build in the dashboard. Run the saved test against each platform to see both results together.
Which React Native testing tools do I still need?
Jest for unit and component tests, and TesterArmy for end-to-end tests on the built binary. Detox, Appium and Maestro become optional: nothing in the app has to be instrumented for the agents to run a flow.
How do I run React Native E2E tests without selectors or testIDs?
Agents work from what is on screen, the way a user does, so accessibility labels and testID props are not required. Describe the flow in plain English and the run follows the visible interface on iOS and Android.
Can I run React Native automated testing in CI without a Mac runner?
Yes. Builds run in cloud iOS simulators and Android emulators, and every pull request gets a GitHub check with a recording. Your CI only uploads the build; no macOS runner sits in the pipeline.
