ew-cli no longer prints garbage to standard out when the API is completely unavailable.ew-cli to 0.9.14testTargets option to the Gradle pluginew-cli to 0.9.14ew-cli now prints errors in a {"error": "some error message..."} object to standard out when running with
the --json flagprintOutput 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.ew-cli correctly, displaying them at build failure.ew-cli to 0.9.13--test-targets and --display-name options to the GitHub action.ew-cli to 0.9.13ew-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.--directories-to-pull. This avoids
marking tests as errors if only some shards produce the files to be pulled.maven.emulator.wtf repository if repositoryManagement is used from the
settings.gradle or settings.gradle.kts file.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.--test-targets-for-shard option now supports all the same operators as --test-targets:
class, notClass, package, notPackage, annotation, notAnnotation, size.--async flag to ew-cli which will make it return immediately after starting the test run. The test results
will be posted back to GitHub when GitHub integration is used. This is useful for CI systems where you want to save build
minutes by running emulator.wtf in parallel with other tasks.pull_request option.async option to Gradle plugin which will make it return immediately after starting the test run. The test results
will be posted back to GitHub when GitHub integration is used. This is useful for CI systems where you want to save build
minutes by running emulator.wtf in parallel with other tasks.ew-cli to 0.9.9run-tests action 0.9.1async flag to the run-tests action, behaviour is similar to the
ew-cli and gradle-plugin options above.ew-cli to 0.9.9Added a new organization settings page in web UI where you can:
20230227)java.lang.NoClassDefFoundError: org/json/JSONObject on newer AGP versionsew-cli to 0.9.8recordVideo option to false in the emulatorwtf {} project extension.ew-cli in the Gradle plugin to 0.9.7emulator-wtf/run-tests v0.9.0recordVideo option to false in the emulatorwtf {} project extension.ew-cli in the GitHub action to 0.9.7library-test to run library module tests (no app apk)outputs to filter what gets downloaded after the test, Defaults to merged_results_xml,coverage,pulled_dirs.record-video to record a video of the test runtimeout to increase or decrease the default 15m test timeout. Minimum 60s, maximum 3h.num-balanced-shards to use sharding based on historical test runtimes.side-effects - your one stop shop to disable error retries and test result cachingnum-flaky-test-attemtps to add repeats to failed shards/jobsfile-cache to disable the APK & test data cache (on by default)file-cache-ttl to fine-tune how long we keep APK files in the cache (1h by default)test-cache to disable the test result cache78.46.71.232 to our outbound IPsNexusLowRes and Tablet10 devicesmodel=Pixel7 devices - an emulator resembling the Pixel 7 phone with it’s 1080x2400 resolution, full list of emulators added:device=Pixel7,version=23device=Pixel7,version=24device=Pixel7,version=27device=Pixel7,version=29device=Pixel7,version=30device=Pixel7,version=31device=Pixel7,version=33device=Pixel7Atd,version=30device=Pixel7Atd,version=31ew-cli --test-targets-for-shard parameter where only the first
target was picked from multiple ;-separated targetsew-cli 0.9.5 where pulling device dirs failed with a crash when downloading the
test resultsAdded ignoreFailures option to the emulatorwtf {} project extension, which will cause the task to not fail the build if
the test run fails. This is useful for CI builds where you want to run tests on multiple subprojects and don’t
want to fail the build if one subproject fails.
NOTE: you can discover whether the build was successfuly either by checking the JUnit XML files or configure the plugin to output a JSON summary of the test result.
ew-cli in the Gradle plugin to 0.9.6ew-cli --prepare option not working with some API token formats--prepare option always returning a non-zero exit codetestWithEmulatorWtf anchor task depending on all of the possible test tasksvariantFilter {} option to the plugin to selectively disable emulator.wtf for certain variants,
example usage:emulatorwtf {
// Do not generate the test task for some specific variants
variantFilter {
if (variant.buildType.name == 'release') {
enabled = false
}
}
}
--num-balanced-shards [value] for fair, historical runtime based sharding:
emulator.wtf will store historical test runtime at a single test level and will assign
tests to shards in the most even way possible, leading to shorter overall test times
than --num-shards or --num-uniform-shards.ew-cli to 0.9.1numBalancedShards property for fair, historical runtime based sharding, see the
ew-cli release notes abovebreaking! ew-cli now outputs a merged JUnit result XML file that combines all of the devices and shards into a single file.
Separate JUnit result XML files, device logcat files or captured videos are no longer downloaded by default - this
helps to cut down on ew-cli runtime, especially for larger test suites with many shards. Logcat and video will
still be captured and viewable in the web UI.
If you need to download these (to store in your CI artifacts for example) you can revert to the old behaviour by adding
--outputs results_xml,coverage,pulled_dirs,logcat,captured_video.
ew-cli version to 0.9.0outputTypes option to the extension DSL--num-flaky-test-attempts
and there were flakes discovered