Where do the Android tests belong?
summary
Examines why many Android projects end up with an inverted test pyramid (heavy UI/end-to-end tests, few unit tests) and the platform-specific obstacles to unit testing. Describes experimenting with design patterns (MVP, MVVM) and testing tools (JUnit, Robolectric, Espresso, Calabash), presents a working app example, and shows a TDD-driven mixed MVP/MVVM pattern and how to place and write tests at each layer to achieve a healthier test pyramid.
AI-written summary · about
chapters (6)
- 0:00Start
- 5:38IMPORTANCE OF TESTS
- 10:34INVERTED TEST PYRAMID
- 15:35WHY LESS UNIT TESTS?
- 29:38BEFORE MODEL-VIEW-PRESENTER
- 33:23MIX OF MVVM AND MVP








