testing-with-espresso-interop

To test Jetpack Compose with Espresso in the same Activity, use createAndroidComposeRule with the host Activity, call rule.waitForIdle() to ensure Compose is ready, then execute Espresso.onView(...) interactions on the test thread to safely verify hybrid UIs.

Espresso onView fails during Compose UI testing when called from rule.runOnIdle or rule.runOnUiThread, or without waiting for Compose synchronization. Call rule.waitForIdle() first and run Espresso directly on the test thread to prevent deadlocks and main-thread failures.

Yes, you can test soft keyboard visibility and Dialog window focus by leveraging the EspressoLink bridge. This synchronization bridge automatically recognizes Compose idling resources for Espresso, enabling reliable interactions across system-level UI elements and Compose boundaries.

No, manual IdlingRegistry wiring is not needed for Compose and Espresso interoperability. The built-in EspressoLink bridge automatically recognizes Compose idling resources, synchronizing both frameworks so you can focus on View hierarchy and Compose semantics interactions.

The best way to test ComposeView embedded in a View hierarchy is using the EspressoLink bridge with optional scoping via onRootWithViewInteraction. This approach correctly targets multiple ComposeView hosts, ensuring accurate synchronization across hybrid Compose and Android View interactions.