Testing: Testing
summary
Claim: strong Kotlin types and language features reduce testing cost by shifting errors earlier to the compiler and IDE. Evidence: ReasonML adoption reportedly cuts bugs from almost daily to monthly. Concrete tools and practices: Kotlin nullability and compiler checks, types as tests, sealed classes limit domains, property and pure-function testing, and using interfaces instead of fragile mocks. Outcome: fewer brittle unit tests, clearer guarantees at compile time, and lower-cost discovery of bugs even though production and integration tests remain necessary.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:48Testing is a process of executing a program with the aim of finding error
- 2:25The devil is in the details.
- 3:01Integration
- 6:16test-induced design damage
- 22:08Typeful Design
- 25:40Algebraic Data Types
- 26:02Sealed Classes
- 35:15Type systems amplify testing
