CI pipelines and mobile builds

Bitrise integration

TesterArmy tests the iOS Simulator build or Android APK from every Bitrise Workflow and gates the pipeline on the results.

START TESTING FOR FREE READ THE SETUP DOCS

[01] Verdict

What gates the pipeline

The Bitrise Workflow builds the simulator app, then a Script Step uploads it and runs testerarmy ci, which waits for every run and exits non-zero when any fails.

Bitrise · Workflow

testerarmy_ios · iOS simulator build

Script Step · upload-app, then ci

git-clone
xcode-build-for-simulator
Script · Run TesterArmy mobile tests

TesterArmy · iOS Simulator run

Reset password from sign-inPassediOS1m 52s

Tap Forgot password on the sign-in screenAct

Enter the test account email and request a reset codeAct

The screen confirms a code was sent to that emailAssert

Enter the code and set a new passwordAct

[02] Setup

How it works

Setup is bitrise.yml plus the Workflow Editor's Secrets tab. The build must produce an iOS Simulator .app or an Android .apk, because an .ipa or .aab will not work.

Add the three values

Add the API key on the Workflow Editor's Secrets tab so it stays masked, and keep the project and group IDs in app.envs in bitrise.yml.

Build a supported artifact

Build iOS with xcode-build-for-simulator and Android with android-build set to build_type apk, because TesterArmy installs the artifact on a cloud simulator or emulator.

Add one Script Step

One Script Step runs the TesterArmy CLI twice: upload-app sends the build, then ci starts the group, waits for every run and exits non-zero on failure.

Read the setup docsThe docs cover secrets, artifact requirements, iOS and Android recipes, the build-once Pipeline, exit codes and troubleshooting.

See it on your own app

START TESTING FOR FREE

[03] Related

Works with

A connected GitHub repository receives the check and pull request comment. GitHub Actions and Expo EAS test mobile builds the same way, and GitLab CI runs groups after web deploys.

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.Expo EASEAS workflows upload a simulator build or APK and trigger a remote test group.GitLab CIA signed group webhook runs a test group after GitLab CI deploys.

[04] FAQ

Questions

The ci command, run from a Script Step after the build, waits for every run and exits 1 when any failed, was cancelled or timed out, so Bitrise fails the Step and the build.

Bitrise produces an iOS Simulator .app or an Android .apk, TesterArmy installs it on a simulator or emulator, and the agents run the group like a real user. An .ipa device build will not work.

You write test steps in plain language in TesterArmy and save them into a group. The Bitrise recipe expects at least one mobile test that has passed a manual run and belongs to that group.

TesterArmy reports through GitHub only, so a connected repository gets a check and a pull request comment. For GitLab or Bitbucket the Bitrise build status is the gate and the evidence lives in the dashboard.

[05] Start on Bitrise

Test the next Bitrise build

One Script Step after the build gives every Workflow a verdict for each run and an exit code Bitrise gates on.