2024-06-09
Test execution
- Added a workaround for a case where tests running on API 34 would get stuck or not start at all
ew-cli to 0.11.0setup-ew-cli to v0.9.10--help more helpful by splitting options into groupsindividual_test_videos output to download each testcase video separatelydevice=Pixel2,version=21device=Pixel2,version=26device=Pixel7,version=21device=Pixel7,version=26device=Tablet10,version=21device=Tablet10,version=26device=NexusLowRes,version=21device=NexusLowRes,version=26device=Monitor,version=21device=Monitor,version=26device=Pixel2Atd,version=34device=Pixel7Atd,version=34device=Tablet10Atd,version=34device=NexusLowResAtd,version=3465.109.54.236 and 135.181.209.62.
If you rely on outgoing IP addresses we recommend automating them - we publish all the outgoing
IP addresses both as JSON and as DNS records. Read more here.emulator.wtf now supports capturing per-test videos!
This has been the most requested feature by far. We now support capturing frame-precise test recordings of individual tests. To enable this we need some help from the instrumentation test runner to capture exact timestamps of the tests.
To enable this feature, make sure you have the record video flag set and add the following library to your Gradle build:
androidTestImplementation("wtf.emulator:test-runtime-android:0.2.0")
Initial public release of wtf.emulator:test-runtime-android:0.2.0.
androidTestImplementation to enable per-test
video recordings (see above)device=Pixel2,version=25device=Pixel2,version=28device=Pixel2,version=32device=Pixel7,version=25device=Pixel7,version=28device=Pixel7,version=32device=Tablet10,version=25device=Tablet10,version=28device=Tablet10,version=32device=NexusLowRes,version=25device=NexusLowRes,version=28device=NexusLowRes,version=32device=Monitor,version=25device=Monitor,version=28device=Monitor,version=32The test run result links now contain a few details about the run:
ew-cli. We now retry failed requests in a more robust way, and we also increased
some of the longer network call timeouts (like file uploads). This should help in cases where you are running many tests
in parallel from the same CI job.ew-cli to 0.10.9ew-cli to 0.10.9setup-ew-cli to v0.9.9model=Tablet10 would capture corrupted video
due to mismatched encoder parameters.--test-target and
it expanded to multiple parametric test cases. This was previously causing the test run to fail
and works now without issue.Atlantic/Reykjavik timezone (same as UTC).
This should improve compatibility with tests that use the system timezone identifier
and don’t support the Etc/UTC timezone identifier.surfaceflinger process and the whole System UI with it,
we’ll trigger an automatic retry of the test run. This is a rare event that may happen with
tests making heavy use of surfaces like utilizing the camera preview. The retry does not add any
billable minutes to your account. NOTE: just like with flaky repeats, we do not attempt any retries
when using the side-effects flag.org.json library to a newer version.emulator-wtf/invoke@v0.9.7 and emulator-wtf/setup-ew-cli@v0.9.8 to use the node20 GitHub Actions runtime.ew-cli to 0.10.7useTestStorageService flag would run all the tests again in
every shard. NOTE: there is a known issue about AndroidJUnitRunner 1.5.2 or earlier, we will now
warn you if you happen to have this combination.--test-targets would not work as expected when used together with balanced sharding.ew-cli fails fast when trying to run tests on an apk containing only ARM binaries - our emulators are x86/x86_64.