Test execution

• Fixed: in a previous release on 2025-07-17 we made a change affecting test runtime order within shards. While ideally this would have no effect we’ve rolled the change back and kept the old test execution order.

Test execution

• Fixed: tests no longer fail with AndroidJUnitRunner ran more tests than expected error when using the test storage service and targeting specific test classes.

ew-cli 0.12.5

• Improved: better upload performance when testing large apk files containing native libraries.
• Fixed: there was a race condition where internet networking was unavailable for a few seconds when using the egress tunnel feature.

gradle-plugin 0.19.3

• Improved: better upload performance when testing large apk files containing native libraries.
• Improved: bumped default ew-cli version to 0.12.5.

Test execution

• Fixed: tests with large apk files sometimes failed with a non-descriptive timeout message.
• Fixed: some skipped tests were erroneously reported as successful instead of ignored in the test results view.

emulator.wtf web app

• Our LLM-powered test failure analysis got a noticeable upgrade, and it should now give more actionable insights.

emulator.wtf web app

• Fixed per-test videos not rendering in the results page

ew-cli 0.12.4

• Emulator sessions: the CLI will now reconnect emulators to adb when the adb server dies while a session is active.

emulator.wtf web app

• Test result page now loads faster, especially for large test runs containing multiple devices and/or shards.

Test execution

• Fixed flaky test repeat attempts when the initial test run was incomplete due to an application crash. When the app crashes on an initial test run the whole shard will be retried to make sure that test coverage is not lost and all tests are executed.

emulator.wtf web app

• Enterprise organization owners can now configure the default role for new users logging in via SSO/SAML using just-in-time provisioning in the organization settings view, under the SSO/SAML settings section.

ew-cli 0.12.3

• Added: added an --dns-override $host=$ip option to ew-cli to override DNS resolution for a specific host
• Fixed: JNA warnings printed to the console when running on JDK 24 or later
• Fixed: ew-cli now passes proxy configuration to wireguard exit node, fixes ew-wg-exit-node timeout when using the egress tunnel feature

emulator.wtf web app

• Added: emulator.wtf web app now supports specific testcase URLs in the form of https://emulator.wtf/o/<orgUuid>/r/<runUuid>/t/<className>/<methodName>. You can use the test details URL as a base to construct URLs like this for linking to specific testcase results directly.

ew-cli 0.12.2

• Infrastructure changes to support upcoming features

Test execution

• Updated JUnit report generation to include the timestamp attribute in <testsuite> elements.

gradle-plugin 0.19.0

• Bumped default ew-cli version to 0.12.1.
• New: added support for passing secret runner arguments via secretEnvironmentVariables, for use with things like tokens, credentials, passwords, etc.
• New: added support for tunneling emulator egress networking to the machine the Gradle build is running on. Read more about this feature here.
• New: integrate with Gradle’s Test Reporting API (Gradle 8.13+) and Develocity’s JUnit importer.

gradle-plugin 0.19.1

• Fixed: secretEnvironmentVariables were not passed to the emulator correctly and had no effect.

ew-cli 0.12.1

• Fixed a possible FileAlreadyExistsException wg-exit-node.edb0f9de race condition when using the egress tunnel.
• Fixed ew-cli occasionally failing to read app or test apk when running on Java 24.

ew-cli 0.12.0

• Added the ability to pass secret runner arguments via --secret-environment-variables, for use with things like tokens, credentials, passwords, etc. These will be passed to the test runner in the same way as --environment-variables, but won’t be visible in the emulator.wtf UI. Alternatively, secrets can be passed in via environment variables having the EW_SECRET_ prefix, e.g. EW_SECRET_foo=bar.
• You can now override the test instrumentation runner used with --test-runner-class.
• Fixed formatting issues when displaying --help.
• Added support for tunneling emulator egress networking access over to ew-cli. Read more about the egress tunnel here.

Test execution

• Fixed a rare case where tests would fail with “Invalid test apk” with certain incrementally built apks emitted by the Android Gradle Plugin.

emulator.wtf web app

• Test classes and methods can now be sorted in the test results page.
• Added indicators to class names to reflect their expanded/collapsed state.

emulator.wtf web app

• The test results page now shows test runtimes for all classes and methods

emulator.wtf web app

• The test results page now has a light mode available
• Improved how the test runs list is rendered on narrower screens

emulator.wtf web app

• Fixed rendering long test run display names in the test runs list

Test execution

• Fixed a very rare case where the emulator would get stuck for multiple minutes before running the tests

emulator.wtf web app

• Fixed an issue where you’d have to login to the emulator.wtf web app twice

Test execution

• Improved the INSTALL_FAILED_NO_MATCHING_ABIS error message so it’s clearer which dynamic library could be the culprit

emulator.wtf web app

• Organization owners now can turn off all AI features across the whole organization with a single toggle

emulator.wtf web app

• Changed the default test result link visibility to private

  NOTE: this affects new accounts only, we did not retroactively apply the new default to older accounts

emulator.wtf web app

• Added a Help button right there in the test results page - a quick and easy way to reach out to us with all relevant metadata regarding any issues you’re having with your tests

Test execution

• Fixed running tests on multiprocess apps where the main process had a non-standard name

gradle-plugin 0.18.1

• Fixed: the anchor assemble task no longer triggers emulator.wtf tests

Test execution

• Improved smart sharding by casting a wider net when there was no strict historical runtime available (e.g. due to changing --environment-variables or such)