Episode

Balancing test coverage without chasing 100 percent

Podcast
No Compromises
Published
Jun 21, 2025
Duration seconds
941
Processing state
not_requested
Canonical source
https://share.transistor.fm/s/08c0276c
Audio
https://media.transistor.fm/08c0276c/a8a863f5.mp3
JSON
/v1/public/podcasts/no-compromises-1309932/episodes/balancing-test-coverage-without-chasing-100-percent
Markdown
/podcast/no-compromises-1309932/balancing-test-coverage-without-chasing-100-percent.md

Actions

  • POST https://stenobird.com/v1/public/podcasts/no-compromises-1309932/episodes/balancing-test-coverage-without-chasing-100-percent/transcription-requests
    Idempotently request low-priority transcript generation for this episode.
  • GET https://stenobird.com/podcast/no-compromises-1309932/balancing-test-coverage-without-chasing-100-percent.md
    Read the agent-friendly Markdown representation of this episode resource.

Summary

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!