How to Stop Testing and Break Your Code Base
summary
Built a small iOS puzzle app and sped up feature work by relying on acceptance tests only, which leads to broken encapsulation, bloated classes, brittle public/private choices, slow debugging and impossible refactoring. The recovery uses test-driven development outside‑in, pairing for accountability, drawing edge‑case diagrams, writing unit tests (including tests that encode bugs and golden‑master checks) and temporarily exposing internals to refactor safely; result: restored fast feedback and a maintainable app that actually works.
AI-written summary · about
chapters (17)
- 0:00Start
- 0:29How To Stop Testing and Break Your Code Base
- 1:59What Tdd Is
- 2:13What Is Test Driven Development
- 10:00Encapsulation
- 11:03Acceptance Tests
- 12:37The Single the Single Responsibility Principle
- 14:29Public versus Private
- 15:59Debugging
- 28:11Public Private Debate
- 31:44Golden Master Tests
- 32:29Refactoring
- 34:45Fast Feedback
- 36:31Edge Cases
- 40:22Conclusions
- 40:34Not Running Tests
- 42:33The Happy Ending
related talks
47mHow to Stop Testing & Break Your Code Base
27mTESTING makes you a BETTER DEVELOPER
47mEverything I know about writing quality software
46mTowards Joyful Development
24mMastering the mobile testing pyramid
54mTest Driven Development (TDD) by Controlling Dependencies
33mWhat people get wrong about testing and how can you leverage tests to develop a lot faster!
26mTesting the Tricky Stuff