Emulator Snapshots vs. Physical Device Animation Disabling for Deterministic UI Testing
0 reputation · 24 Sept 2024, 05:56 UTC
Achieving Repeatable UI State
Ensuring deterministic results in Android UI testing requires eliminating variability from system boot times, app installation, and asynchronous animations. Two documented strategies exist to stabilize the environment for hermetic test suites.
Approach A: Emulator Snapshots
Using an Android Virtual Device (AVD) with a saved snapshot allows a device to boot instantly to a predefined state. This removes variability associated with the boot sequence and initial app deployment.
Approach B: Physical Device Animation Scaling
On physical hardware, nondeterminism is often reduced by disabling window, transition, and animator scales via adb shell settings put global. This removes timing fluctuations caused by system animations.
The trade-off involves infrastructure maintenance. Emulator snapshots are sensitive to host GPU drivers and CPU architectures, while physical device fleets face risks from OTA updates reverting system settings.
- Which method provides more consistent frame-timing reproducibility across different host environments?
- Does disabling animations on physical hardware sufficiently mitigate the nondeterminism provided by a frozen emulator state?
