How to Stop Testing & Break Your Code Base
summary
An iOS hobby game called SquareFill accumulates bugs and slows development after unit tests are dropped in favour of only high‑level acceptance tests. Missing unit tests hide problems in a shuffleShapes routine, confuse two coordinate systems (pixels vs grid units) and make refactoring hazardous. Retroactive outside‑in testing plus pair programming and TDD restore fast feedback, reveal edge cases, let small pieces be verified quickly, keep the test suite green and make productionising spikes and refactors safe and repeatable.
AI-written summary · about
chapters (20)
- 0:00Intro
- 4:17SquareFill
- 8:07A lack of tests causes pain
- 9:35Encapsulation
- 10:18Acceptance tests & encapsulation
- 11:14SRP (Single Responsibility)
- 12:18Public vs private
- 13:16Debugging
- 20:03Fast feedback
- 21:17Edge cases
- 22:55Productionising spikes
- 25:27Path to a solution
- 33:00TDD makes everything better
- 36:34Debugging
- 39:14Refactoring
- 40:55Fast feedback
- 44:11Edge cases
- 44:33Productionising spikes
- 45:24Summary
- 46:39Outro
related talks
44mHow to Stop Testing and Break Your Code Base
27mTESTING makes you a BETTER DEVELOPER
54mTest Driven Development (TDD) by Controlling Dependencies
42mDon't Let Your Tests Flake Out
26mTesting the Tricky Stuff
01h 02mThe Unit Tests Strike Back: Testing the Hard Parts
33mWhat people get wrong about testing and how can you leverage tests to develop a lot faster!
23mUI Testing for Fun and Profit