running-tests-on-gradle-managed-devices

Run reproducible Android instrumented tests by provisioning Gradle Managed Devices in CI/CD pipelines, which automatically boots version-controlled emulators and tears them down after execution to ensure environment parity.

Gradle Managed Devices handle emulator lifecycle management by automatically provisioning, booting, executing tests on, and tearing down virtual devices, eliminating the need for manual AVD management and ensuring consistent test matrices.

Configure automated test sharding on Android emulators by defining device specifications and test matrices directly in your Gradle build files, allowing consistent execution across multiple provisioned managed devices.

You can use Automated Test Device (ATD) images for headless Android test execution to significantly reduce build times and resource consumption in CI pipelines while maintaining reproducible test results.

Running instrumented tests on Gradle Managed Devices works for local development workflows by ensuring developer machines run tests on identical, version-controlled device configurations defined in build files, matching CI environments.

Android emulator tests fail inconsistently across environments due to manual AVD management and configuration drift; defining reproducible test matrices with Gradle Managed Devices ensures identical API levels and system images everywhere.