CI pipelines and mobile builds

Expo EAS integration

TesterArmy tests every Expo EAS build on cloud iOS Simulators and Android emulators and reports on the pull request.

START TESTING FOR FREE READ THE SETUP DOCS

[01] Verdict

What the workflow returns

The EAS workflow builds the iOS Simulator app, uploads it and runs the saved test group. The TesterArmy run report lists every step with its result.

Expo EAS · testerarmy-mobile-tests.yml

.eas/workflows/testerarmy-mobile-tests.yml

on pull_request to main

build_ios
upload_ios_app
run_ios_tests

TesterArmy · iOS Simulator run

Browse catalog, add to cartPassediOS1m 52s

Open the Shoes category from the home screenAct

Open the first product and pick a sizeAct

The detail screen shows the same price as the listAssert

Add the product to the cart and open the cartAct

The cart shows one item in the chosen sizeAssert

[02] Setup

How it works

The API key, project ID and group ID come from the TesterArmy dashboard, and the Integrations tab must connect the project to its GitHub repository before checks and comments appear.

Set the EAS environment variables

Store the TesterArmy API key as an EAS secret and add the project ID and group ID from the dashboard as EAS environment variables.

Add two EAS build profiles

Add an iOS Simulator profile and an Android APK profile to eas.json, because TesterArmy tests .app Simulator builds and .apk files rather than .ipa or .aab.

Add the EAS workflow

Commit the workflow that builds each platform, uploads the artifact with the TesterArmy CLI and runs the saved group on pushes and pull requests to main.

Read the setup docsThe docs cover environment variables, build profiles, workflow variants and a prompt block a coding agent can follow.

See it on your own app

START TESTING FOR FREE

[03] Related

Works with

GitHub receives the workflow's checks and comments. GitHub Actions and Bitrise run the same upload and test steps from their own pipelines, and Linear turns found issues into tickets.

GitHubThe GitHub App posts checks and comments on every pull request preview.GitHub ActionsUpload an iOS Simulator or Android build and run a mobile test group.BitriseBitrise builds the app, hands it to TesterArmy and gates the pipeline on results.LinearIssues the agents find become Linear tickets through one shared project-wide connection.

[04] FAQ

Questions

An EAS workflow builds the iOS Simulator app or Android APK, uploads it to TesterArmy and runs a saved mobile test group on every push and pull request to main.

With the project connected to its GitHub repository in the Integrations tab, each pull request gets a check and a comment, and each push to main gets a check on the commit.

The Fingerprint + Repack variant calculates Expo fingerprints, finds a compatible iOS Simulator or Android APK build, repacks it with the current JavaScript bundle and falls back to a full build when nothing matches.

You write test steps in plain language and the agents carry them out on a cloud iOS Simulator or Android emulator, returning a pass or fail verdict with a per-step transcript and a video recording.

[05] Start on Expo EAS

Test the next EAS build

Add the workflow once and every push and pull request to main builds, uploads and tests the app on cloud simulators and emulators.