With Sauce Runner for Real Devices, you can run tests using the Espresso and XCUITest frameworks, run tests in parallel across multiple devices, and run subsets of tests against specific devices. This topic describes the options you can use with the runner. You can set the options as environment variables that can be referenced in your testing scripts, or pass them as command line parameters, which will take precedence over options set as environment variables. You can also create a runner configuration file with the options and commands for running your tests.
Only Available in TestObject
At the moment, the Sauce Runner is only available for our Legacy Real Device Cloud Platform, check the Real Device Testing in Sauce Labs Feature Preview for updates on when the Sauce Runner will be available.
What You'll Need
- A Sauce Labs account and access to your account credentials
- A native app (both debug and non-debug app)
- Have Sauce Runner downloaded and installed
|Defines a configuration YAML file where the runner executes based on the parameters set in the file. Please note, if you decide to use the config command you can no longer use any of the command options below. For more information please read the following wiki page: Creating a Sauce Runner for Real Devices Configuration File.|
|X||The API key for your Sauce Labs real device cloud account.|
|X||The path to the |
|X||The path to the |
The Data Center endpoint to use in your tests. For Espresso and XCUITest, you'll need to choose from either the US or EU data centers. For more information, see Data Center Endpoints.
If you don't specify a device or devices for your test, one will be assigned to your tests based on the type of application you're testing against.
|For static allocation of a device, provide the ID for the type of device to use in your tests, such as 'iPhone_5_real'. You can find the IDs for devices on the Live Testing page in the Sauce Labs web interface. Under the Real Devices tab, search for the type of device you want to use, and then click the Details link in the device description to see the device ID. See Examples of Device Specifications for the Real Device Runner for more information.|
|The list of devices, allocated dynamically or through static description of the device ID, to use in your tests. See Examples of Device Specifications for the Real Device Runner for more information.|
Set a custom test name to appear on the UI, Default is
|If you are using Sauce Connect Proxy, provide the identifier of the tunnel you want to use.|
|Interval in seconds to check test results. Default is |
|Test timeout in minutes. Test duration cannot exceed 60 minutes. Defaults to |
|The folder for the JUnit XML output.|
|Provide the URL of an alternative REST endpoint to use. See Data Center Endpoints.|
|For dynamic allocation of a device, provide an operating system version to use. For example, use |
If set, only private devices will be queried.
If set, only phones will be queried.
If set, only tablets will be queried.
For dynamic allocation of a device, provide the device name you would like to dynamically allocate. For example, use
Provide a comma separated list of test cases or test classes.
If you want to run all tests of a class, provide only the classname. If you want to run a specific method of a class, provide the class name and method name separated with a '
If set, the instrumentation will start with Test Orchestrator version 1.1.1 in use.
NOTE: with Test Orchestrator, it is in most cases recommended to also add the "
Provide a list of test options to Espresso. The key-value pairs supported by espresso are documented here: https://developer.android.com/studio/test/command-line#AMOptionsSyntax. In the example, the test would execute all test methods defined in the class
Example: Execute all tests in class TestClassA
Example: Execute a specific test in class TestClassB
Using Sauce Runner with a Proxy
If you need Sauce Runner to connect to the internet through a proxy server, use the
-D command to specify a direct domain connection to your proxy server and port. The parameters http.proxyUser and
http.proxyPassword are optional and can be used if the proxy needs authentication: