The Journey of Testing
summary
ConvertKit finds JavaScript coverage under 20% and sets a squad goal to reach 50%, requiring every PR to add at least one test (even a render test). The team wires Coveralls into PRs for immediate coverage feedback, starts pairing sessions and stricter reviews, and tracks a simple line chart of coverage. Coverage climbs incrementally, sometimes drops when feature work bypasses tests, and never magically reaches 90%, but the process makes regressions easier to catch and refactors safer.
AI-written summary · about
chapters (14)
- 0:00Introduction and speaker background
- 1:51Athletics mindset in software
- 3:01Testing myths and misconceptions
- 5:31Overcoming testing procrastination
- 8:10Starting small with testing goals
- 9:57ConvertKit’s testing journey
- 13:09Balancing feature work and testing
- 16:14Implementing PR testing requirements
- 18:30Team collaboration on testing
- 21:05Testing in new vs. legacy projects
- 22:03Business case for testing
- 24:11Empathy and team growth in testing
- 25:01Responding to failure and pushback
- 26:17Final thoughts and encouragement
related talks
14mKover Your Code: A Practical guide to Android Test Coverage
27mQuest for Adequate Autotest Coverage
32mHow to Improve Test Coverage to 80% with Generated Unit Tests and Stay Calm
46mSpeed Up PR Tests with Smart Code Coverage-Based Selection
03mTest coverage
33mDevs should love your tests
44mStrategy for Acing Continuous Testing in DevOps
20mThe Road to Continuous Testing