2023-03-18
ew-cli 0.9.2
- fixed
ew-cli --prepare
option not working with some API token formats - also fixed the
--prepare
option always returning a non-zero exit code
ew-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 discoveredew-cli
now has exit codes indicating various failure modes--num-flaky-test-attempts
option to ew-cli
to re-attempt running failed devices
and/or shardsew-cli
now cache their results properly.device=Pixel2,version=33
device=Tablet10,version=33
device=NexusLowRes,version=33
device=Monitor,version=33
--no-test-cache
or --side-effects
to disable this behaviour.23.88.5.162
to our outbound IPsLaunched emulator.wtf web app to help you with:
com.android.test
) subprojects.
When using these make sure the targetProjectPath
is configured in the android {}
block.ew-cli
now supports capturing a video recording of the test -
pass both --record-video
and --outputs-dir
, a recording.mp4
file will
be saved per device-job combinationAll network traffic from emulators now originates from these IP addresses:
See the documentation for further details and machine-readable endpoints for getting these.
Added API 24 emulators
Complete list of new combinations added:
device=Pixel2,version=24
device=Tablet10,version=24
device=NexusLowRes,version=24
Fixed rendering of result links in GitHub Action logs by switching token format
ew-cli
will skip uploading files if they
have been recently added, enabled by default for 1h. Use
--no-file-cache
to disable and --file-cache-ttl <duration>
to control the behaviour.--prepare
flag that only uploads files to populate cache but doesn’t trigger
any tests.--library-test
parameter
instead of --app
and --test
to test library modules.Added Android Automated Test Device (ATD) images with API 31. Read more about ATD images here.
Complete list of new combinations added:
device=Pixel2Atd,version=31
device=Tablet10Atd,version=31
device=NexusLowResAtd,version=31
ew-cli
no longer prints errors with Zulu 11 JDK