controlling-the-test-clock

To manually advance the Jetpack Compose test clock frame by frame, you use a MainTestClock control mechanism to drive recomposition and animation cycles, ensuring deterministic animation validation in UI tests.

Jetpack Compose UI tests fail with a ComposeTimeoutException due to non-deterministic timing and frame-delay issues; you can resolve this by explicitly managing the TestCoroutineScheduler to drain queued tasks.

Fix stale state reads and race conditions in Compose v2 UI tests by stepping the MainTestClock forward after state mutations to synchronize the Recomposer and process all pending changes.

Yes, you can use the MainTestClock to verify animation states at specific intervals by manually driving the test clock forward, which allows precise frame-by-frame animation validation.

Limitations of manually controlling the test clock in Jetpack Compose include the necessity to explicitly drain queued tasks after state mutations to avoid race conditions and ensure the Recomposer processes all pending changes.