Test execution

• Fixed an issue where sharding together with the useTestStorageService flag would run all the tests again in every shard. NOTE: there is a known issue about AndroidJUnitRunner 1.5.2 or earlier, we will now warn you if you happen to have this combination.
• Also fixed a case where --test-targets would not work as expected when used together with balanced sharding.

ew-cli 0.10.8

• We now display branch names and PR links in the test results list view. This makes it easier to understand which branch and PR a test run is associated with. The PR link is clickable and will take you to the PR on GitHub. This feature is available for test runs started after this release.

emulator.wtf web app

• The test runs page is now the default homepage in the emulator.wtf web app instead of the tokens page.

ew-cli 0.10.6

• ew-cli fails fast when trying to run tests on an apk containing only ARM binaries - our emulators are x86/x86_64.

Test execution

• Fixed an issue where certain webpages could crash the whole emulator, leaving tests in a broken state.
• We also improved our detection of various emulator failure scenarios.

ew-cli 0.10.5

• Pulled directory sizes are now logged correctly in ew-cli output.

Emulators

• Emulators on API levels 33 and 34 can now benefit from GPU acceleration. Use the gpu=auto flag (e.g. --device model=Pixel2,version=34,gpu=auto) to enable GPU acceleration. Read our blog post on the benefits of GPU acceleration here.
• Disabled GPU acceleration for Automated Test Device images. These devices do not benefit from GPU acceleration, and it was causing issues.

ew-cli 0.10.4

• When using the --json flag or the summary output format, the consumed test run minutes are now available in the JSON outputs of test runs. The consumed test run minutes are available under the billableMinutes key in the JSON output. This is useful when estimating the cost of using emulator.wtf in the long-term. Read more on how we calculate billableMinutes here.

emulator.wtf web app

• The Usage view in the emulator.wtf web app now defaults to the past 30 days instead of showing usage from the beginning of the current calendar month.
• Fixed a bug where canceled test runs during the apk upload phase would show up as perpetually running in the emulator.wtf webapp test runs list view.

emulator.wtf web app

• The audit log can now be exported either as a CSV or a JSON file. The file contains a log of all the actions taken by users in the emulator.wtf web app. NOTE: audit log is an enterprise plan only feature.

Test execution

• Added validation of uploaded APK files to prevent corruption issues due to incomplete uploads. This issue compounded with the test file cache where we would keep the corrupted apks around and future test files would be corrupted as well.

emulator.wtf web app

• Google Workspaces is now a first-class citizen in our SSO/SAML login flow. Read the integration docs here. NOTE: enterprise plan only.

emulator.wtf web app

• Improved markdown rendering in the AI-powered test failure helper to better handle code blocks and lists.

emulator.wtf web app

• Fixed flaky tests sometimes still showing up as failed in test runs list.

emulator.wtf web app

• Organization owners can now disable public test result links. This is useful when you want to keep your test results private and only accessible to your team members. NOTE: the setting does not apply retroactively, so any existing public test result links will remain accessible.

emulator.wtf web app

• Fixed the login UI in emulator.wtf getting stuck on errors (i.e. wrong password or network errors).

ew-cli 0.10.3

• Re-release of 0.10.1 with minification issues fixed.
• Increased APK size limit from 500 MiB to 700 MiB.

ew-cli 0.10.1

• Increased APK size limit from 500 MiB to 700 MiB. NOTE: this version has minification issues, use 0.10.3 or newer instead.

ew-cli 0.10.2

• Rolled back to 0.10.0 binary due to minification issues in 0.10.1.

Emulators

• We’ve added support for ATD emulators with API versions 32 and 33. Also, ATD images for API 31 are available again. List of device combinations added:
  • device=Pixel2Atd,version=31
  • device=Pixel2Atd,version=32
  • device=Pixel2Atd,version=33
  • device=Pixel7Atd,version=31
  • device=Pixel7Atd,version=32
  • device=Pixel7Atd,version=33
  • device=Tablet10Atd,version=31
  • device=Tablet10Atd,version=32
  • device=Tablet10Atd,version=33
  • device=NexusLowResAtd,version=31
  • device=NexusLowResAtd,version=32
  • device=NexusLowResAtd,version=33
  • See all available emulator images here.

Test execution

• Fixed a case where test runs that use a custom faulty AndroidJUnitRunner would get stuck.

Test execution

• Fixed emulator.wtf erroring out when retrying flaky tests with commas in their names or parameters

gradle-plugin 0.15.1

• Fixed the collectEmulatorWtfResults task not using the proxy configuration supplied via emulatorwtf {} block or the system properties

ew-cli 0.9.19

• Added --collect-results command to ew-cli. This will download the results of a previous run (invoked with --async --json) and save them locally. Useful for more advanced integrations making many ew-cli invokes in parallel.

gradle-plugin 0.15.0

• Bumped default ew-cli to 0.9.19
• Gradle plugin now runs tests out of band from Gradle workers when configured with async = true. This frees up the workers to perform ordinary build tasks and allows running more tests concurrently.
• Added collectResultsTaskEnabled option to the Gradle plugin configuration. This adds a collectEmulatorWtfResults task to the project which can be used to fetch the results of all submodule tests (invoked with async = true). Useful for more advanced integrations making many ew-cli invokes in parallel.

ew-cli 0.9.18

• You can now run tests on GPU-accelerated emulators by adding gpu=auto to the --device option. Our preliminary internal benchmarks point to a roughly 2x performance improvement when using GPU-acceleration. This will use GPU-acceleration whenever possible. Use gpu=software to force use of software GPU. Today, emulator.wtf defaults to software rendering if gpu isn’t specified, but we’ll soon default to GPU-acceleration. NOTE: today GPU-acceleration is available on API versions 23, 24, 27, 29, 30, 31. It is not yet available on 33 or 34.

emulator.wtf web app

• Fixed an issue where a flaky test would erroneously show up as a failure in the results

Emulators

• We’ve added support for API 34 (Android 14) emulators. You can now run tests on the latest Android version! Full list of device combinations added:
  • device=Pixel2,version=34
  • device=Pixel7,version=34
  • device=Tablet10,version=34
  • device=NexusLowRes,version=34
  • device=Monitor,version=34

Emulators

• API 31 ATD emulators have been removed due to stability issues in the system image.

ew-cli 0.9.17

• Added --shard-target-runtime option to ew-cli. It’s a new sharding mode where you specify the overall runtime instead of the number of shards. E.g. a 10-min test suite will spawn 5 shards and finish around 2 minutes when invoked with --shard-target-runtime 2m
• When running with --num-flaky-test-attempts we no longer re-run whole shards but only the tests that failed. You can revert to the whole behaviour by adding --flaky-test-repeat-mode all.

GitHub action emulator-wtf/run-tests@v0.9.6

• Bumped default ew-cli to 0.9.17
• Added shard-target-runtime and flaky-test-repeat-mode options, see above for the description

gradle-plugin 0.14.0

• Bumped default ew-cli to 0.9.17
• Added shardTargetRuntime and flakyTestRepeatMode options, see above for the description

gradle-plugin 0.13.3

• Fixed a case where the Gradle plugin would use arm-architecture APK files even when x86 APK splits were available