Writing Truly Testable Code
summary
Covers how to design and refactor software so it becomes testable: techniques for building testability into new architecture and for refactoring legacy code that wasn’t designed for tests. Uses examples referencing Android, MVP, Kotlin and Rx but presents language- and platform-agnostic approaches applicable beyond those technologies.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:47Why write tests
- 3:31Testing main goals
- 5:58First rule of testable code
- 8:47Second rule of testable code
- 13:05Third rule of testable code
- 15:38Explicit versus implicit I/O
- 18:48Dependency controllability
- 23:59Replacing singletons and statics
- 26:45Platform abstraction
- 34:14Implementation details and duplicates
- 36:46Gradual shift to testable code
- 39:15Integration tests and summary
- 41:23Breaking rules and balance
- 42:06Q&A
related talks
50mWriting Testable Code
28mDesign for Testability
55mUnit Testing Like a Pro - Towards a Testable Design
41mHow to Really Test an Android Application
30mRefactoring and Test Fakes: Crafting Resilient Code with Confidence
20mThe Art of Testing
47mTestable Architecture: How to Build High-Quality Software and Ship Fast
01h 01mYou Can Test Anything