Solving the Problems of Espresso Android Autotests in the Real World
summary
Practical guidance for improving Espresso UI tests for Android apps with large existing codebases: techniques to lower the onboarding threshold for team members, design a simple clear UI-test architecture, stabilize tests and handle flakiness without changing the app architecture, and integrate tests into CI with understandable reporting. All solutions are demonstrated on a concrete demo app (source on GitHub) so teams can reuse the implementations.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 2:00Choosing autotest tool
- 3:08Espresso vs UI Automator
- 5:59App code access
- 8:08Engaging devs
- 10:59Espresso for big projects
- 11:19Test maintenance
- 15:17Stability and reporting
- 16:01Readable tests
- 17:29DSL for Espresso
- 19:38Kotlin extensions
- 24:35Handling waits
- 26:20Unstable tests with FileHandler
- 30:14Sync app and test
- 33:25Simplified IdlingResource
- 37:22FileHandler + IdlingResource
- 38:07Parallel test runs
- 39:31Flaky test causes
- 40:54Flaky test strategy
- 41:58Useful autotests
- 42:40Test maintenance
- 43:21Allure reporting
- 46:57Debugging tests
- 47:37Conclusion
related talks
53mSolving Espresso Android Autotest Issues in the Real World
44mTaking care of your UI tests
44mEfficient testing UI Android apps by example
33mAndroid UI Testing & Challenges
31mFurther Speeding Up UI Tests (Espresso)
46mEfficient Android UI Testing
43mAndroid Apps Testing in 2019
23mManaging your UI tests simply and effectively