Testable Android Architecture
summary
Claims a concrete architecture called MVPC (modified MVP) that splits activity as controller, presenter (logic), and model (data) so half the app does not touch Android. Tests use JUnit + Mockito (local JVM) for fast unit tests, Robolectric as integration tests, and Espresso for end-to-end UI; login presenter examples show synchronous testing by calling thread.run, mocked account validator, and a test controller. Sample app lives in ecgreb mvpc and presenter lifecycle and view-state manager strategies handle rotations.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:56Testing on Android
- 2:13Clean Architecture
- 4:25Activity
- 4:45Life Cycle
- 13:01Views
- 17:39Which Framework Do You Use the Most for Unit Testing on Android
- 18:04The Test Pyramid
- 23:36Decoupled Mvpc Architecture Unit Testing
- 24:59Login Presenter
- 27:19Writing an Integration Test
- 34:43Legacy Code
- 37:41Choose an Architecture Appropriate to Your Use Case
- 39:44Constructor Injection
related talks
35mBuilding better Android apps with MVP
39mClean app design with Architecture Components
30mArchitecting an app with MVP and ViewModels
39mMVP: The Life-Changing Magic of Tidying Up Your Android Presentation Layer
41mHow to Really Test an Android Application
28mHands-on Android Architecture & Architecture Components
47mClean app design with Architecture Components
32mEffective Android Architecture