controlling-the-test-clock

What problem does it solve?

It solves the confusion of how Compose UI tests progress through time—especially when animations, recomposition, and async coroutines depend on the test clock—so your assertions match what the framework actually did.

Core Features & Use Cases

• Frame-accurate clock control: Advance time by exactly one frame with MainTestClock.advanceTimeByFrame, or step by durations with the correct rounding rules.
• Deterministic animation timing: Understand the 16 ms frame model and the “kick-off” frame so animations start with the right play time.
• v1 to v2 migration reliability: Use runCurrent or advanceTimeBy(0) after state mutations when v2 createComposeRule queues work under the StandardTestDispatcher.
• Test-clock waiting & failure diagnosis: Use advanceTimeUntil for Compose-state conditions and correctly interpret ComposeTimeoutException as a verdict on unmet snapshot/state changes.

Quick Start

Use the controlling-the-test-clock skill to explain why your Compose test clock needs an extra advanceTimeByFrame after setContent and how to fix timing issues caused by v2 task queuing.