The 7 Stages of Unit Testing
summary
Seven stages map to concrete practices: Kotlin live coding builds a SuperVillain data class and three passing unit tests (return value, state, behavior) using Android Studio, Kotlin live coding, and JUnit4 + mockito (mockito‑kotlin); claims include a recommended test mix of ~70% behavior, 20% state, 10% return value, and using Robolectric only for instrumentation; shows DI patterns (constructor first), dagger‑generated code is not tested, and coverage is measured but can be gamed.
AI-written summary · about
chapters (15)
- 0:00Start
- 1:34Selfish Unit Tests
- 4:48Use Unit Testing Incrementally
- 7:02Good & Bad News
- 8:33Follow the rules
- 10:03Types of Unit Tests
- 28:52TDD Schools
- 29:42Test Doubles
- 32:17Use a Mocking Framework
- 32:37Dependency Injection
- 33:45Depression
- 34:52Coverage in Android Studio
- 36:02And when I have too many tests?
- 36:52Acceptance & Hope
- 37:08Evolve
