Android UI Testing & Challenges

Review of Android's UI testing framework - Espresso. How software developers can utilize it and test automation engineers as well. Scaling from the laptop to the CI environment and sharding. All of these require solid tooling support. and stability. Demonstrating the power of Android Studio and test recorder. In the end, reviewing the challenges - topics that are hard by default to test on the Android platform for test automation and manual QA.

Transcript

1. Android UI Testing & Challenges. Merab Tato Kutalia Android GDE, Chapter Lead & TBC Bank @TatoKutalia
2. Tools • UIAutomator • Espresso
3. Espresso • Runs on device/emulator • High speed and stability • Test Recorder • Tooling • Scaling
4. Espresso How it works Espresso handles a low-level task — it finds the required element on the screen according to the specified parameters (ViewMatcher), and executes an action with it (ViewAction) or performs a check (ViewAssertion).
10. Espresso How it works All Espresso commands are executed in the same process in which the application under test is running. Conditions to be met: The message queue is empty. There are no instances of AsyncTask currently executing a task. All developer-defined idling resources are idle.
11. Espresso MessageQueue
12. Demo
13. Espresso scenarios • ActivityScenario • FragmentScenario
14. Espresso • IdlingResource?
15. Scaling • CI (Firebase Test Lab + other vendors) • Test Sharding
16. Common challenges • Navigation • Deeplinks • Analytics • Backups
17. Resources • Medium blog • Espresso docs • Sharding • Setup emulator for testing • Flank • ConditionWatcher
18. Thanks