Testing Jetpack Compose UI

on YouTube ↗30m

" summary

Claims that Jetpack Compose testing differs from View testing: no view hierarchy, declarative UI, no IDs but Modifier.testTag and semantic properties, and tests run synchronized by default. Uses the Compose testing library (versus old Espresso flows), exercising UI with find/matchers, performClick and assertIsDisplayed, verifying text and navigation. Demonstrates setting initial state for composables in tests. Notes a real-world issue with singleInstance activities and fixes by providing a test-specific manifest or build variant.

AI-written summary · about

" chapters (7)

1. 0:00Introduction
2. 1:30Compose vs traditional UI
3. 8:53Testing button clicks
4. 16:26Navigation and state testing
5. 22:54Reusing test composables
6. 26:06Fixing instrumentation issues
7. 29:00Q&A

" related talks

• 36mTesting Jetpack Compose UIDmytro Shuba · droidcon San Francisco 2022
• 34mOverview of UI testing in ComposeMichael Bailey · droidcon New York 2022
• 33mHow to Test Your Compose UIIstván Juhos · droidcon Berlin 2022
• 05m5 ways Compose improves UI testingJose Alcérreca · Android Dev Summit 2022
• 46mTesting Compose Anew: Simplicity, Reliability, FlexibilityAleksey Tyurin · Mobius 2025 Spring
• 29mComposing With ConfidenceAdam McNeilly · droidcon New York 2022
• 47mDancing Around the Semantics Tree: UI Testing Compose ScreensPavel Strelchenko · Mobius 2024 Autumn
• 07mWrite your first Compose UI testJolanda Verhoef · Android Dev Summit 2022