Real Device Testing with Espresso and XCUITest

Espresso and XCUITest are the test automation frameworks for writing and testing user interface (UI) functionality for Android and iOS mobile apps, respectively.

Our Sauce Runner for Real Devices test runner provides you the ability to run these tests on our Real Device Cloud without having to leave your Espresso or XCUITest environment.

  • Leverage the power of our 2,000+ Android and iOS devices.
  • Accelerate and scale your test volume quickly and effectively through parallel test execution on multiple devices at once.
  • Gain immediate insight with test reporting comprised of videos, screenshots, and logs.

What You'll Need#

  • Your Sauce Labs username and access key.
  • Your mobile app file and mobile test file. Accepted file types are .ipa for iOS and .apk for Android.

If you'd like to try out this functionality but don't have an app on hand, download our Sauce Labs demo app file and test file. :::

System Requirements#

  • Have Java 8 or later installed on your local machine. To check the version, run java -version on your local machine.

Download Runner#

  1. To get started, click the button below to download the Sauce Runner for Real Devices jar file. Sauce Runner for Real Devices is parameterized for use in your local CI/CD environment. It will connect your environment to our Real Device Cloud.

Set Up Project Folder#

  1. Unzip the download package contents to your local machine. The actual runner file will be in the bin folder.

  2. Create a new folder for your project and drop the saucelabs-native-test-runner application, your app .apk file, and test .apk file here, so that your folder structure looks like this:

    |_{root / your project folder}

Gather Your Credentials#

  1. Find your Sauce Labs username, accessKey, and the emulator deviceName you wish to test on. The list of devices is located under Live > Cross-Browser > Mobile Real.
  • Set Environment Variables (Optional): Setting your Sauce Labs username and accessKey as environment variables provides an extra layer of security for your credentials when you reference them from within your tests.

Configure Your Test#

  1. There are two ways to configure your Espresso or XCUITest tests to run on Sauce Runner for Real Devices: use the CLI or create a YAML configuration file.

Using the CLI#

CLI Reference

See Sauce Runner for Real Devices CLI Reference. To view these commands in your CLI, run the --help option:

java -jar saucelabs-native-test-runner.jar --help

Open a new command line window, then add the required commands and flags to your test script:

Required Commands and Flags
java -jar saucelabs-native-test-runner.jar xcuitest --username $SAUCE_USERNAME --accessKey $SAUCE_ACCESSKEY --datacenter US --app <path-to-app> --test <path-to-test>
Basic Example
java -jar saucelabs-native-test-runner.jar espresso --username john.smith --accessKey ab015c1e-xxxx-xxxx-xxxx-xxxxxxxxxxxx --datacenter US --app SauceLabs.Mobile.Sample.Espresso.App.apk --test SauceLabs.Mobile.Sample.Espresso.Tests.apk

Sauce Runner will install the Android app, SauceLabs.Mobile.Sample.Espresso.App.apk, on the Google Pixel emulator and then launch the Espresso test suite, SauceLabs.Mobile.Sample.Espresso.Tests.apk.

If needed, you can also add optional parameters. See Sauce Runner for Real Devices CLI Reference to view the full list of available parameters. Sauce Runner for Real Devices will execute tests based on the parameters you set.

Using a YAML Config File#

Below are some examples of how to write your YAML file. See Sauce Runner YAML Configuration for a full list of available parameters. This YAML file example includes all required parameters for running Espresso and XCUITest test suite with Sauce Runner for Real Devices, plus the following options:

  • devices: use this to specify a group of devices via dynamic allocation (using regex) and/or static allocation (regex plus exact device ID). See Static and Dynamic Device Allocation for detailed instructions.
  • testsToRun (XCUITest only): use this to set a specific set of classes/tests to run on a device. The class(es) specified can be written in Swift or Objective-C.
  • envs (Espresso only): use this to set a specific set of classes/tests to run on a device. The class(es) specified can be written in Java or Kotlin.

Both examples show parallel test execution: four separate parallel tests on four different Android/XCUITest devices.

  • The tests within the section will be assigned to that one device and executed in the order specified.
  • For each section starting with the - datacenter directive, a new parallel test thread will spin up for the device indicated. If you specify multiple test classes or test methods, each will be executed serially, in the order presented in the section, on the device.

Espresso YAML File Example

See full example on GitHub

More Examples:

Parallel execution using dynamic devices
See full example on GitHub
Run in parallel on hard-coded devices
See full example on GitHub

Once you're finished writing your YAML file, be sure to save it.

Run Your Test#

  1. Open a new command line window, then add and execute the following required commands and flags. This will launch the Sauce Runner connection and begin running your test.

Wait for the runner to upload both files and execute the tests on Sauce Labs real devices. Our emulators are capable of running Espresso jobs for up to three hours, however, a one-hour execution time is recommended.

Required Commands and Flags
java -jar runner.jar config --path <your YAML file name> --accessKey <your Sauce access key>
Basic Example
java -jar runner.jar config --path My.YAML.File.yml --accessKey ab015c1e-xxxx-xxxx-xxxx-xxxxxxxxxxxx
  1. Wait for the client to submit the tests. The test runner will automatically upload the apps you've specified. The expected output will be something like this:

    Basic Example Response
    Finished uploading app file 'binaries/android/sample-android-app.apk' to 'US' data center.
    Uploading test file 'binaries/android/sample-android-test.apk' to 'US' data center...
    Finished uploading test file 'binaries/android/sample-android-test.apk' to 'US' data center.
    Starting test run on US data center...

    The maximum execution time for a single XCUITest test is one hour. As a best practice, we recommend designing your tests as small, atomic, autonomous, and setting maximum execution times in minutes or seconds, so you can get the most efficiency for your builds.

  2. Once the test suite has completed, you can view your test results on Sauce Labs under Automated > Test Results > Real Devices. Test results for each device rolled into a single set of artifacts (e.g., videos, logs) and you can download these artifacts via the API.

Go to the Sauce Labs Training GitHub repository to browse more example scripts and Espresso test cases on Sauce Labs Emulators.

Legacy RDC (TestObject)#

As an alternative to using the built-in upload behavior of Sauce Runner for Real Devices, you can separate the upload of your app and test files via the TestObject Storage API.

Implementing the separation of upload allows you to take control of when to upload a new version, which in turn helps save time by reducing the total amount of file uploads done.

Below are example curl snippets for uploading your app build and test runners to TestObject.

curl -u "username:APP_APIKEY" -X POST -H "Content-Type: application/octet-stream" --data-binary @/path/to/iOSApp.ipa

Additional Resources#

Last updated on by Kim