Starting a test run

A test run is an execution of a test suite with an application binary. This section describes how to upload and start a test run in App Center Test. Before creating a test run, complete the steps at Getting started with App Center Test.

Test runs are started by executing a command that invokes the App Center command line interface (CLI). The command can be executed from a local development or test computer or as part of a continuous integration or continuous deployment system. This uploads your application and tests to App Center Test where they execute and generate a test report. Some of the command parameters vary based on your application platform, test framework, the test devices and other test configuration options. To generate a prototype command, use the New test run dialog in App Center Test.

App Center Test

  1. Login to the App Center Portal.
  2. Select an application.
  3. In the navigation area on the left, select Test (the circle with a check mark icon).

You’ll see a high-level overview of existing test runs for the selected application and the New test run button.

New test run

Click the New test run button to start the dialog that creates the test run prototype command. This dialog advances through three screens.

  1. Select devices - select the devices to test against.
  2. Configure - select the test series, system language and test framework to use for the test.
  3. Submit - provides the prototype command to start a new test run based on the previous selections.

Move between these screens by completing selections or the Next > and < Previous buttons.

Select devices

Select the devices or a named device set to test against. A device set is a collection of devices and operating systems. If you previously named and saved a device set that you wish to use for this test select it from the list of named device sets.

Otherwise, click Choose other device configurations then choose the device or devices to use from the list. To save the selected devices as a named device set, click Save set and provide a name. To proceed without saving this selection as a named device set, click Select N devices (The value for N changes as you make device selections to confirm the number of devices selected).


Select the test series, the system language, and the test framework. The system language determines the device locale that affects system-level device settings, such as the decimal separator. For more on test series, see App Center Test Core concepts.


Based on the previous steps a prototype command is generated. Some parameters in this prototype command must be edited to match your environment before using it to upload and start your test run. For example, the command prototype generated for a hypothetical user and an Android app with Espresso tests might look like:

appcenter test run espresso --app "user_org_key/App_key" --devices 36608302 --app-path PATH_TO_FILE.apk  --test-series "master" --locale "en_US" --build-dir PATH_TO_ESPRESSO_BUILD_FOLDER


The command shown here is for illustration purposes only. Do not use this command. Instead, use the dialog to generate a command prototype for your application, test framework and test parameters.

The command parameters include:

  • app - The id of the selected application in App Center. This value should not be modified.
  • devices - The id for the selected device set to execute against. If you selected a named device set the id is generated based on the device set name. If you are not using a named device set the id is generated as a device slug. A device slug is a unique hexadecimal value representing the selected collection of devices and operating systems. This value should not be modified.
  • app-path - The path to the application being tested. This must be edited to match your environment and can be an absolute or relative path.
  • test-series - The selected test series. The test series is a label used to group related test runs together in App Center Test reports.
  • build-dir - The path to the directory that contains your test automation build output. This must be edited to match your environment and can be an absolute or relative path.

Edit the app-path and build-dir in the generated command to match your environment then execute it using the command line or terminal window. You may want to save the command to use for future test runs.

The edited and ready to use version of the command line for this hypothetical example could be:

appcenter test run espresso --app "user_org_key/App_key" --devices 36608302 --app-path "app/build/outputs/apk/debug/app-debug.apk"  --test-series "master" --locale "en_US" --build-dir "app/build/outputs/apk/androidTest/debug"

Getting help

You can always contact us through the blue chat icon in the lower-right hand corner. We do not provide 24/7 support, but will strive to reply as fast as possible.

If you want help with a test run, navigate to the test run in question and copy the URL from your browser and paste it into the support conversation. A test run URL looks like something like