auditing-compose-test-suite

Jetpack Compose UI tests flake on CI due to timing, idle resource, or finder issues. A structured test suite audit reviews setup, semantics finders, and assertions to diagnose configuration correctness and identify CI-specific failures.

To audit Jetpack Compose tests, run a six-phase review checking setup, finders, assertions, actions, timing, and debug output. This non-mutating analysis produces a prioritized issue list to identify slow or incorrect test logic.

The best way to find high-severity issues in Compose test suites is enforcing safety rules that flag Thread.sleep and deprecated performGesture. A multi-phase audit routes these findings to specific fixes for actionable improvements.

Yes, you can review existing Compose Test.kt files through a non-mutating audit that generates a prioritized issue list and guidance. This approach diagnoses flakiness and slowness safely without editing your test code.

Yes, a Compose test audit checks semantics finder discipline and assertion strength across six phases. It evaluates configuration correctness, action correctness, timing behavior, and actionable debug output to ensure reliable test execution.

You need to audit your Compose test suite for flakiness when tests behave differently between local and CI runs, after migrating between Compose test APIs, or when you want to know what test logic to rewrite next.