Run your first mobile test

Run your first mobile test

Upload a simulator build of your native iOS or Android app and run your first test on it. The suite you pick sets the OS version, and you can follow the run live.

Before you start

  • Build your app for a simulator. Pie runs mobile apps on simulators and emulators, so a build made for a device won’t work. To make one for Android, native iOS or React Native iOS, see Prepare mobile builds.
  • Get your mobile app into a Pie workspace. If you see Book a call and Request access instead of a dashboard, your workspace isn’t ready yet.
  • Store a test login if your app needs one. See Credentials.

Upload the build

In the sidebar, select Builds, then Upload your first build. Drag the file in or select Choose File, enter a Build ID and select Submit for testing.

Upload a simulator .app, zipped with ditto. An .ipa file won’t work.
Upload an .apk file.

Use a Build ID you haven’t used before, with no forward slash. When the upload finishes, the build appears in the Builds table.

Open New Run

In the sidebar, select Run History, then New Run in the page header.

Choose the build and suite

Pick your build in Select Build, then a suite in Test suite. If suites were set up with your Pie contact during onboarding, they’re in the list. No suite yet? Select Choose or create a test suite.

The suite sets the OS version, and on iOS the device too. To test on another one, change it in the suite’s How it runs. See Organize tests into suites.

Start the run

Select Start Run. Pie opens the run so you can follow each step live.

What you’ll see

The run opens live. A status card counts Tests completed, Steps taken, Pass, Fail and Issues found as Pie works. When the run ends, open it from Run History to see each test and its step screenshots.

If the run can’t start, Pie tells you what to change. If it seems stuck, see Troubleshooting.

Do this from your agent or API

Your agent finds a build with get_builds and starts a run with create_run and the buildId. Over HTTP, upload with POST /v1/app/builds and start with POST /v1/runs.

Next steps

Last updated on