Skip to content

disable-animations.md

Latest commit

 

History

History
70 lines (52 loc) · 1.75 KB

disable-animations.md

File metadata and controls

70 lines (52 loc) · 1.75 KB
Raw

Animations

You can turn off device animations during a test run. On Android this works by zeroing the three system animation scales (window, transition, animator) via adb. On iOS this enables the Reduce Motion accessibility setting.

Usage

Whole upload

Pass the flag on dcd cloud:

dcd cloud ... --disable-animations

Or set it once in the workspace config.yaml:

platform:
  android:
    disableAnimations: true
  ios:
    disableAnimations: true

Per test (both platforms)

Override the upload-wide setting for a single flow via the DeviceCloud env variable:

# in your test.yaml
appId: my.app
env:
    DEVICECLOUD_OVERRIDE_DISABLE_ANIMATIONS: true
---
# test steps

Per test, platform-specific

When the same flow YAML runs on both Android and iOS, you can target each platform independently. Use this when animations cause problems on one platform but you want them on for the other (for example, animations off on Android to fix scroll/tap flakiness, but on for iOS where Reduce Motion changes app appearance):

# in your test.yaml
appId: my.app
env:
    DEVICECLOUD_OVERRIDE_ANDROID_DISABLE_ANIMATIONS: true
    DEVICECLOUD_OVERRIDE_IOS_DISABLE_ANIMATIONS: false
---
# test steps

The other platform's key is ignored — only the one matching the run's platform is consulted.

Precedence

When more than one is set, the most specific wins:

  1. DEVICECLOUD_OVERRIDE_<PLATFORM>_DISABLE_ANIMATIONS (per test, this platform)
  2. DEVICECLOUD_OVERRIDE_DISABLE_ANIMATIONS (per test, both platforms)
  3. The upload-wide --disable-animations flag or config.yaml
  4. Default: animations are on

A false override is honoured the same as true — a test can opt out even when the upload-wide flag is set.