Pragmatic Coverage Targets and Maintenance Costs

#58 - Principles for Writing Valuable Unit Tests - Vladimir Khorikov

Topic 11 of 18

Published Oct 4, 2021 · Clip 21:07–23:40 (2:33)

Vladimir argues no specific coverage number fits all projects and that mandated coverage targets (e.g., failing builds below 80%) introduce perverse incentives like low-value or assertion-free tests. He recommends high coverage (~90%) only for the domain model and using coverage numbers as alerts, not gates. Brittle tests are the most notorious source of maintenance cost.