Building Android Testing Infrastructure
summary
Builds a working CI recipe: upload APKs with gcloud → Firebase Test Lab, shard instrumentation and robo runs with Flank (yaml shards, retry counts), run smoke tests on PRs via annotations, and push results to TestRail. Use Fladle/Flank docker or gradle wrapper for CI. Move UI checks into unit space with Paparazzi (git LFS, record vs verify), test Room migrations with JDBC helpers, and detect Gradle regressions with Gradle Profiler nightly scenarios.
AI-written summary · about
chapters (12)
- 0:00Android testing intro
- 3:12UI test automation with Firebase Test Lab
- 6:21Parallel tests with Flank
- 8:47Fixing flaky UI tests
- 10:54Scheduling tests in CI
- 13:44QA collaboration with TestRail
- 14:04Unit testing best practices
- 18:33Affected unit tests in CI
- 21:02Snapshot testing Paparazzi
- 24:11Room migration unit tests
- 28:26Gradle build regression detection
- 33:19Summary and resources
related talks
27mGra Fi Te: Leveraging Gradle and Firebase for Android Testing
32mBuilding Quality Android Apps for the Future with Continuous Integration
45mParallel testing of Android UI on a large scale
35mTesting Firebase Android SDKs at Google
26mAndroid CI: 2016 edition
22mThese 5 Firebase tools will help you test and run your app with confidence
36mAndroid like a (reliable) Rock Star - All About Android Continuous Integration
39mIndustrialize your Android Tests: a Tools and Methods Cookbook