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.
ew-cli now prints errors in a {"error": "some error message..."} object to standard out when running with
the --json flag
gradle-plugin 0.12.1, 0.12.2
Added a printOutput option to the Gradle plugin which will print the output of the ew-cli command to standard out.
This is useful for debugging issues with the plugin without having to resort to the noisy --info flag.
The Gradle plugin now shuttles errors from ew-cli correctly, displaying them at build failure.
ew-cli now fails early if your app or test apk minSdkVersion is not supported by the selected devices. This avoids
wasting time on test runs that are guaranteed to fail.
Tests no longer error out when a device doesn’t have a directory specified by --directories-to-pull. This avoids
marking tests as errors if only some shards produce the files to be pulled.
gradle-plugin 0.12.0
Gradle plugin no longer adds the maven.emulator.wtf repository if repositoryManagement is used from the
settings.gradle or settings.gradle.kts file.
Added a project property (wtf.emulator.addrepository=false) to bypass adding the repository completely, even if the
plugin would add the repository manually. When using this you should either add the https://maven.emulator.wtf/releases/
repository manually or provide the ew-cli binary in some other way.
Scaleup plan upgrade is now available to all users via self-service. You can upgrade
to this plan from the billing page in the emulator.wtf web app
Added GitHub SSO support. Your GitHub team members can now access your emulator.wtf organization directly without
having to go through email invites (scaleup plan only).
The --test-targets-for-shard option now supports all the same operators as --test-targets:
class, notClass, package, notPackage, annotation, notAnnotation, size.