Listen "Balancing test coverage without chasing 100 percent"
Episode Synopsis
Joel and Aaron unpack how they use code-coverage numbers as a starting signal rather than a finish line. They discuss realistic thresholds, choosing the right tool for each test layer, and why coverage metrics can double as negotiation leverage inside big organizations. Listen in for practical ways to decide what to test—and when to stop.(00:00) - Testing passion vs. shipping work
(01:00) - Coverage tells you what’s missing
(03:45) - Picking a baseline metric that grows
(06:15) - Draw the line between logic and UI tests
(12:45) - Silly bit
Want help getting started with your test coverage? Going from 0% to 1% is the hardest step. We can help!
More episodes of the podcast No Compromises
Why I changed my mind about down migrations
03/01/2026
Why senior developers feel wrong more often
20/12/2025
Should you ever hand-format code?
06/12/2025
Discussing different ways to model data
22/11/2025
Read outside tech to expand your horizons
08/11/2025
Should you use DTOs in Laravel?
27/09/2025
Sunsetting a company app without loose ends
13/09/2025
ZARZA We are Zarza, the prestigious firm behind major projects in information technology.