What people get wrong about testing and how can you leverage tests to develop a lot faster!
summary
Claim: testing enables safe large refactors — one week rebuilding Sourcery’s parser by replacing SourceKit with SwiftSyntax produces 10,000 additions and 21,000 deletions with minimal breakage because tests caught regressions. Practical rules: prefer test-driven development (red‑green‑refactor), write behavioral tests not implementation checks, and use mocks not real network to avoid flaky slow suites. Target fast isolated tests (aim under one second), add tests for bugs and critical business paths, and use tools like Sourcery, SwiftyMocky, CustomDump and snapshot testing.
AI-written summary · about
chapters (8)
- 0:00Testing introduction
- 2:49Testing misunderstandings
- 7:05TDD best practices
- 13:22Testing anti-patterns
- 18:18Maintainable tests
- 24:40Legacy code testing
- 29:37Key takeaways
- 31:47Q&A
related talks
16mEffective Strategies for Testing and Releasing Server Side Changes
56mIf You Won't Test Your Code, Who Will?
26mTesting the Tricky Stuff
25mAdopting a Test driven Mindset in the Workplace
32mThinking in tests
43mUnselfish Testing
29mHow I Learned to Stop Worrying and Love Unit Testing
44mTesting the untestable - patterns and use cases analysis