Testing in Practice: Keeping Your Tests Concise and Declarative

on YouTube ↗29m

" summary

Argues that mocks cause brittle, interaction-only tests and recommends replacing them with Kotlin idioms: factory functions for injectable constructors, functional interfaces for one-line fakes, and small focused interfaces so fakes remain simple. Shows tests that keep behavior inside a single function body, prefer object-to-object assertions over fragile property checks, and use Compose screenshot testing for pixel diffs. Claims these changes reduce setup noise, expose poor architecture, and make tests declarative and maintainable.

AI-written summary · about

" chapters (17)

1. 0:00Testing philosophy intro
2. 1:49Automated testing types
3. 3:13Unit tests and design
4. 8:51Mock-heavy test critique
5. 11:41Kotlin factory functions
6. 13:06Functional interfaces
7. 14:33Shared state avoidance
8. 15:59DAMP vs DRY
9. 17:00Why code is better than documentation
10. 19:49Self-documenting tests
11. 20:32Faking context
12. 21:13Interface segregation
13. 22:40Test naming
14. 23:43Kotlin object mocking
15. 24:25State vs properties
16. 25:51Mock-free testing tips
17. 27:17Outtakes

" related talks

• 27mDe-mock your testsJarosław Michalik · droidcon Berlin 2022
• 19mHow to write a mock-free appRonaldo Pace · droidcon Berlin 2025
• 30mRefactoring and Test Fakes: Crafting Resilient Code with ConfidenceAsh Davies · Droidcon London 2023
• 37mBeyond the Mockery: Why We Should Embrace Testing Without Mocking FrameworksAsh Davies · droidcon Berlin 2023
• 36mBest Practices for Unit Testing in KotlinPhilipp Hauer · KotlinConf 2018
• 31mBeyond the Mockery- Why We Should Embrace Testing Without Mocking FrameworksAsh Davies · droidcon New York 2023
• 41mMocks vs Fakes vs StubsMateusz Herych · GDG DevFest Sofia 2019
• 32mTesting with KotlinJarosław Michalik · Mobilization 8