New: instrumentation tests with Orchestrator

Android Test Orchestrator runs each of your app's instrumentation tests independently, which has several benefits, but also one drawback:

Benefits

No shared state: Each test runs in its own Instrumentation instance, so shared state doesn't accumulate across tests.

Isolated crashes: If a test crashes, it takes down only its own instance of Instrumentation, so the other tests in your suite still run.

Drawback

Longer runtime: Each test running its own Instrumentation instance means that the testing process takes slightly longer overall. The increased run time could impact your quota usage or billed time and might cause you to hit devices' time-out limits.

Test Lab always uses the latest version of Orchestrator. To enable Orchestrator, select Run with Orchestrator from the Advanced options screen in instrumentation test setup.

Note:Run Orchestrator locally before trying it in Test Lab. To avoid spending quota on or getting billed for malfunctioning tests, confirm that Orchestrator is working in your app by running a test on your own machine before uploading your APK.

Investigate your test results

When the test starts, you're automatically redirected to the test results page.
Tests can take a number of minutes to run, depending on the number of different
configurations you have selected and the test timeout duration set for your
tests. After your tests have run, you can review test results. See
Analyzing Firebase Test Lab Results to learn more
about how to interpret the test results.