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.
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 billableMinuteshere.
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.
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.
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.
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.
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.
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.
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.
We’ve finally added test result listing! After signing in to emulator.wtf you can browse
the history of all of your tests and navigate to their respective results pages.
Fixed --display-name errors when running the action
The emulator-wtf/run-tests GitHub action now depends on the pinned versions of
the emulator-wtf/setup-ew-cli and emulator-wtf/invoke subtasks. If you depend on an
exact version (e.g. emulator-wtf/run-tests@v0.9.5) then you’ll be using fixed and
deterministic versions of all the emulator.wtf GitHub Actions.
