Efficient UI testing in Android
summary
Combines end-to-end, functional and screenshot testing so you keep a few slow E2E checks, run many pixel tests, and run medium numbers of isolated UI tests; functional tests save roughly 3 seconds per case by avoiding navigation. Uses ActivityScenario, launchFragmentInContainer, Compose test rule, screenshot comparison with Shot and Paparazzi differ (Shot runs on device, Paparazzi runs on JVM), plus parameterized tests and a screen-robot DSL to prepopulate DB, reduce flakiness, and cut manual verification time.
AI-written summary · about
chapters (7)
- 0:00Start
- 22:56READABILITY
- 25:22FLAKY TESTS
- 29:46LEARN YOUR TOOLS
- 34:46DIFFERENT APPROACHES
- 34:57PRE-POPULATING THE DATABASE
- 36:17REAL DATA VS FAKE DATA
related talks
44mEfficient testing UI Android apps by example
38mThe Testing Pyramid – What does it mean for Android?
33mAndroid UI Testing & Challenges
23mManaging your UI tests simply and effectively
43mUI testing is so easy - said no developer ever
29mHow to Shorten UI Test Run Times
35mEasy screenshot testing with Compose
43mAndroid Apps Testing in 2019
