Testing Firebase Android SDKs at Google
summary
Describes concrete practices: unit tests use Robolectric on JVM, target 80% line coverage, integration tests run hermetically on emulators, UI acceptance tests use Espresso and UIAutomator against pre‑prod backends, and CI runs pre‑ and post‑submit. Measures are numeric and repeatable: binary size as a delta, startup latency deltas from process start to onPreDraw, memory deltas and leak checks, and battery measured on real devices with the Monsoon battery lab.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:14What is Firebase
- 3:40Platforms
- 4:12Test Pyramid
- 6:03Test Types
- 8:00Unit Tests
- 9:20Integration Tests
- 11:22SDK Testing
- 11:51UI Tests
- 14:10Compatibility Test
- 16:44Testing Types
- 17:12Binary Size
- 19:58Memory
- 21:05Battery
- 22:37Device or Emulator
- 23:45Firebase Test Lab
- 25:01Thank you
- 25:35Latency
related talks
26mDevelop Rock-Solid Apps with Firebase
22mThese 5 Firebase tools will help you test and run your app with confidence
26mAndroid CI: 2016 edition
44mWhat makes good unit tests for Android apps
46mBoost the Quality of Your App with Firebase
46mEfficient Android UI Testing
43mAndroid Apps Testing in 2019
41mAndroid Testing Bootstrap