ew-cli 0.9.7

• Fixed a bug in ew-cli --test-targets-for-shard parameter where only the first target was picked from multiple ;-separated targets

ew-cli 0.9.6

• Fixed a regression introduced in ew-cli 0.9.5 where pulling device dirs failed with a crash when downloading the test results

gradle-plugin 0.9.3

• Added 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.

gradle-plugin 0.9.4

• Bumped default ew-cli in the Gradle plugin to 0.9.6

ew-cli 0.9.5

• We switched our minify stack from Proguard to R8, resulting in a rough 33% reduction in the size of the ew-cli binary

ew-cli 0.9.3

• broken release due to a bug in the Proguard minified, do not use

ew-cli 0.9.4

• reverted changes introduced in 0.9.3

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

gradle-plugin 0.9.2

• the Gradle plugin now runs different application variant tests in parallel using the Gradle workers
• the plugin now creates a testWithEmulatorWtf anchor task depending on all of the possible test tasks
• added variantFilter {} 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
      }
    }
  }
  

emulator.wtf web app

• fixed really annoying browser back behaviour where it was hard to return from a results link
• fixed incorrectly displaying failed tests as flaky with some test runs

ew-cli 0.9.1

• added --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.

gradle-plugin 0.9.1

• bumped default ew-cli to 0.9.1
• added numBalancedShards property for fair, historical runtime based sharding, see the ew-cli release notes above

ew-cli 0.9.0

• breaking! 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.

gradle-plugin 0.9.0

• Bumped default ew-cli version to 0.9.0
• Added outputTypes option to the extension DSL

emulator.wtf web app

• The test results web UI now displays flaky tests with a separate icon if test was run with --num-flaky-test-attempts and there were flakes discovered

ew-cli 0.0.51

• ew-cli now has exit codes indicating various failure modes
• added --num-flaky-test-attempts option to ew-cli to re-attempt running failed devices and/or shards

ew-cli 0.0.50

• Tests that add additional data files with ew-cli now cache their results properly.

emulator.wtf web app

• Completely revamped the results web UI. Read the blogpost here.

Emulators

• Added API 33 emulators, full list of all emulators added:
  • device=Pixel2,version=33
  • device=Tablet10,version=33
  • device=NexusLowRes,version=33
  • device=Monitor,version=33
• Fixed capturing coverage when using the test service storage

ew-cli 0.0.49

• emulator.wtf now caches test results, as long as the app and test apks are byte-for-byte the same and the test arguments haven’t changed. Use --no-test-cache or --side-effects to disable this behaviour.

gradle-plugin 0.0.13

• The emulator.wtf Gradle plugins are now fully cacheable, even when using a remote cache.

Emulators

• Fixed a race condition where sometimes API 24 emulators wouldn’t start properly
• Added 23.88.5.162 to our outbound IPs

Emulators

• Emulators are now always in the UTC timezone
• Fixed an issue where emulator clocks were sometimes off by months, failing tests relying on SSL cert validity periods

emulator.wtf web app

Launched emulator.wtf web app to help you with:

• inviting more users to your organization
• managing the access levels organization members have
• creating and rotating API tokens and see their usage
• tracking your usage over time
• configuring details like credit-card billing

gradle-plugin 0.0.12

• The Gradle plugin now picks up isolated Android test (com.android.test) subprojects. When using these make sure the targetProjectPath is configured in the android {} block.

ew-cli 0.0.48

• 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 combination

Emulators

• All network traffic from emulators now originates from these IP addresses:

  • 148.251.112.247
  • 176.34.140.8

  See the documentation for further details and machine-readable endpoints for getting these.

docs.emulator.wtf website

• Created a separate documentation page: https://docs.emulator.wtf

Emulators

• 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 0.0.47

• Added APK and input file caching to tests - 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.
• Added new --prepare flag that only uploads files to populate cache but doesn’t trigger any tests.

Test execution

• Fixed use of androidx test services to capture screenshots