2026-06-08
Emulators
- Added
77.42.115.125and65.109.17.223to our outbound IPs. There will be a grace period of two weeks before we start sending traffic from these addresses. - Removed
157.180.105.69from our outbound IP address list.
77.42.115.125 and 65.109.17.223 to our outbound IPs. There will be a grace
period of two weeks before we start sending traffic from these addresses.157.180.105.69 from our outbound IP address list.ew-cli could stall for minutes before running any tests.ew-cli version to 1.3.2.ew-cli version to 1.3.2.ew-cli version to 1.3.2.Important
emulator-wtf/run-tests@v1.0.0-rc02:emulator-wtf/actions/use-emulator@v1.0.0 action to make use of a generic adb-connected emulator in your workflows.emulator-wtf/actions repository has immutable releases.GITHUB_REF_NAME env var when running in GitHub Actions.ew-cli version has been bumped to 1.3.0.emulator-wtf/run-tests@v0.9.11:We’ve made a bunch of breaking changes in v1.0.0. Read more about the 1.0.0 release and breaking changes.
GITHUB_TOKEN as the token is no longer supported. Please switch to OIDC authentication instead. Read more here.ew-cli version to 1.3.0.ew-cli version to 1.3.0.ew-cli instances with --egress-tunnel.withDeviceTest {} is declared after the plugins {} block.com.android.kotlin.multiplatform.library plugin (AGP 9 KMP Android library), automatically creating testAndroidMainWithEmulatorWtf and related tasks.ew-cli version to 1.2.2.--scm-* parameters are now correctly honored and missing ones are guessed from environment when running on CI.GITHUB_REF_NAME env var when running in GitHub Actions.process failed to attach crashes on API 34.egressLocalhostForwardIp now properly forwards the value to ew-cli instead of crashing.--shard-unit flag with a test_classes option that ensures all test methods within a class run on the
same shard (defaults to test_methods).shardUnit configuration option to control sharding granularity. Can be set to ShardUnit.TEST_CLASSES to
shard at the test class level, or ShardUnit.TEST_METHODS (default) to shard at the test method level.ew-cli version to 1.2.0.shard_unit option to control sharding granularity. Can be set to either test_classes or test_methods
(default), where test_classes will place whole test classes on the same shard, and test_methods will shard at the
test method level.ew-cli version to 1.2.0.device=Pixel2,version=36device=Pixel7,version=36device=NexusLowRes,version=36device=Monitor,version=36device=Tablet10,version=36device=Pixel2Atd,version=36device=Pixel7Atd,version=36device=NexusLowResAtd,version=36device=Tablet10Atd,version=36--testcase-duration-hint to provide an average test-case runtime hint for --shard-target-runtime or --num-balanced-shards. More info: here.ew-cli no longer hangs if setting up an adb session fails.testcaseDurationHint. More info: here.ew-cli version to 1.1.0.testcase-duration-hint. More info: here.ew-cli version to 1.1.0.testcase_duration_hint, num_balanced_shards and shard_target_runtime. More info: here.ew-cli version to 1.1.0.--shard-target-runtime uses a better heuristic for guessing the number of shards when there’s no historical data available.ew-cli no longer checks for WRITE_EXTERNAL_STORAGE permission when both coverage and test storage service are enabled.testTargetsString property on the emulatorwtf {} dsl.
Note that this will override any test targets specified via the testTargets property or the targets {} dsl.WRITE_EXTERNAL_STORAGE permission when both coverage and test storage service are enabled.ew-cli version to 1.0.6.locale parameter of the --device option.ignoreFailures to true now only ignores test failures as
promised in the Javadoc.ew-cli version to 1.0.5.configurations {} block to the emulatorwtf {} dsl to enable multiple test run configurations within the same module.New emulator-wtf/emulator-wtf@0.0.3 orb with support for CircleCI OIDC, read more here.
android.newDsl=false and android.newDsl=true modes.android.newDsl setting.