Testable Android Architecture
summary
A modified MVP architecture called MVPC separates Android‑dependent code (activities, system services, lifecycle) from pure logic and data so presenters run as plain JVM classes and survive config changes by re‑registering with new controllers; unit tests use JUnit + Mockito to swap out a network interface (the demo sleeps 2s but tests mock it), view tests run on Robolectric, async work uses Thread whose run method is invoked synchronously in tests, and the sample trims a generated 700‑line activity down to ~95 lines.
AI-written summary · about
chapters (8)
- 0:00Introduction and welcome
- 2:22Evolution of Android testing
- 4:30Problems with activity-centric apps
- 9:22Clean architecture approach
- 14:25Separating Android and non-Android code
- 18:18Testing Android vs non-Android parts
- 21:19Code walkthrough and demo
- 33:54Q&A session
