CI pipelines and mobile builds

GitHub Actions integration

TesterArmy tests every iOS Simulator or Android build from GitHub Actions and writes the verdict to the step summary.

START TESTING FOR FREE READ THE SETUP DOCS

[01] Verdict

What the action returns

The workflow builds the app and the action uploads it, provisions a cloud simulator or emulator, runs the mobile test group and writes the verdict to the step summary.

GitHub Actions · iOS Mobile Tests

iOS Mobile Tests

pull_request · tester-army/mobile-github-action@v1

upload
defined_tests
dynamic_agent

TesterArmy · iOS Simulator run

Tap the profile icon in the top right and open SettingsAct

The order notifications toggle is visible and offAssert

Turn the toggle on and return to the home screenAct

Settings shows the toggle still on after reopeningAssert

[02] Setup

How it works

Setup is three repository secrets and one workflow file. The group must already hold a mobile test that you ran once by hand, or nothing runs.

Add three repository secrets

Store the API key from API Keys under Profile, the project ID from Project Settings and the group ID from the test group menu.

Build and upload the artifact

Build the iOS Simulator .app or Android .apk in a dedicated job, upload it as a GitHub artifact and download it on a Linux runner.

Run the mobile action

Add the TesterArmy mobile action with the app path and platform so it uploads the app, runs the group, waits for results and cleans up.

Read the setup docsThe docs carry full iOS and Android workflow files, action modes, the parallel PR agent split and troubleshooting.

See it on your own app

START TESTING FOR FREE

[03] Related

Works with

A GitHub connection lets the dynamic PR agent read each pull request. Expo apps belong on Expo EAS, Bitrise uses the CLI flow, and web deploys use the group webhook.

GitHubThe GitHub App posts checks and comments on every pull request preview.Expo EASEAS workflows upload a simulator build or APK and trigger a remote test group.BitriseBitrise builds the app, hands it to TesterArmy and gates the pipeline on results.CI webhooksJenkins, Buildkite, CircleCI or a shell script triggers a group with one request.

[04] FAQ

Questions

Build the iOS Simulator app or Android APK in one job, then the TesterArmy mobile action uploads it, runs the test group on a cloud simulator or emulator and returns a pass or fail verdict.

You write mobile tests in plain language in TesterArmy, run each once by hand and add them to a group. The action then runs that group against every new build.

The dynamic PR agent explores what a pull request changes and can run alongside the defined group. With GitHub connected it can skip irrelevant changes, report them as cancelled and leave the PR unblocked.

The action accepts an iOS Simulator .app or .app.zip and an Android .apk, and zips a .app directory. An .ipa, .aab or .xapk will not work, and every run executes on a simulator or emulator.

[05] Start in GitHub Actions

Test the next mobile build

Add three secrets and one workflow file, and the next iOS Simulator or Android build comes back with a verdict in the step summary.