2023-06-07
emulator.wtf web app
- 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.
--display-name
errors when running the actionemulator-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.https.proxy*
system properties in addition to http.proxy*
ew-cli
to 0.9.16proxyHost
, proxyPort
, proxyUser
and proxyPassword
, in addition to manual
configuration the [standard Java http.proxy* system properties](https://docs.oracle.com/javase/8/docs/api/java/net/doc-files/net-properties.html#Proxies
will be picked up automatically--proxy-host
, --proxy-port
, --proxy-user
and --proxy-password
options
to configure the use of a https proxy when hitting emulator.wtf APIsew-cli
now prefers IPv4 networking when both IPv6 and IPv4 networking are availableew-cli
to 0.9.15ew-cli
no longer prints garbage to standard out when the API is completely unavailable.ew-cli
to 0.9.14
testTargets
option. Use something like
testTargets = 'class foo.bar.Baz'
to only run tests in the foo.bar.Baz
class.
See the full options here: https://developer.android.com/reference/androidx/test/runner/AndroidJUnitRunner#typical-usageew-cli
to 0.9.14
ew-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.13
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.--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
.Fixed flaky tests not being displayed correctly if a test suite spanned multiple devices and shards
Added an option to log in with GitHub OAuth to emulator.wtf web UI.
Fixed PR comments not showing up for GitHub Actions builds triggered with the pull_request
option.
--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.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.9
async
flag to the run-tests
action, behaviour is similar to the
ew-cli
and gradle-plugin
options above.ew-cli
to 0.9.9
Added a new organization settings page in web UI where you can:
LLM powered test failure explanations!
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.7
recordVideo
option to false
in the emulatorwtf {}
project extension.ew-cli
in the GitHub action to 0.9.7
library-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=23
device=Pixel7,version=24
device=Pixel7,version=27
device=Pixel7,version=29
device=Pixel7,version=30
device=Pixel7,version=31
device=Pixel7,version=33
device=Pixel7Atd,version=30
device=Pixel7Atd,version=31
ew-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.6