Demystifying Code Through Testing
summary
Three scenarios cover practical tactics and outcomes: when a code base has no tests the plan is why buy setup — justify with a quantified outage cost, get manager and team buy‑in, and wire up a test framework and CI/CD pipeline; when tests are slow or flaky focus on metrics test types clean code — measure time and failure rates, separate unit vs integration (avoid spinning up DBs in unit tests), and refactor for simpler, testable code; when tests are healthy maintain consistent coverage (aim ~80–90%, treat <50% as an improvement opportunity).
AI-written summary · about
chapters (6)
- 0:00Introduction
- 2:52Why tests matter
- 5:43Adding tests to no-tests codebase
- 8:56Improving bad tests
- 16:33Maintaining good tests
- 21:11Summary
related talks
56mIf You Won't Test Your Code, Who Will?
42mIntroducing the benefits of the testing diamond
37mUnderstanding the successes and the pain points of different testing strategies
37mClean Test Code
11mNeed For Tests: Most Wanted
40mA Tale of Unit Tests, Code Coverage and Code Design
42mUse testing to Develop Better Software Faster
48mTesting is Confidence - A Developer's Perspective