Android CI: 2016 edition
summary
Classification of Android tests into fast JVM unit tests, slower instrumentation tests and slowest end-to-end tests guides which to automate and which to cut; the recommended test pyramid favors heavy unit coverage and minimal end-to-end. Uses Robolectric to run SDK-dependent code on the JVM, Espresso for activity-level instrumentation, and UIAutomator/Appium for device-level flows. CI patterns: Jenkins with emulators/real devices, STF/device-farms (STF 2.0 adds REST API), or container CI plus third-party device farms; one production setup mixes patterns 1 and 3.
AI-written summary · about
chapters (7)
- 0:00Android CI intro 2016
- 2:00Android test types
- 8:45Android test tools
- 15:34Test automation strategies
- 19:10Android CI patterns 2016
- 23:51Choosing Android CI setup
- 25:38Conclusion and key takeaways
related talks
41mAndroid Testing Bootstrap
34mSetting up Android UI Testing on CI
43mAndroid Apps Testing in 2019
39mIndustrialize your Android Tests: a Tools and Methods Cookbook
35mTesting Firebase Android SDKs at Google
38mAndroid Basics: Continuous Integration
44mEfficient testing UI Android apps by example
42mProduction Level Test Driven Development and What's new