Code coverage can be a tricky metric to make sense of. Our approach is to use code-coverage numbers as a starting signal rather than an end result.
In the latest episode of the No Compromises podcast, we 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
And after listening, don't forget to subscribe to the podcast, so you don't miss future episodes.
Here to help,
Joel
P.S. I think we can all agree 0% test coverage is too low. Let's help you fix that!