We often use coverage as if it were a quality indicator… but do we really know what we're measuring? Code coverage, requirements coverage, branch coverage, decision coverage?
The problem is that when we don't have this clear, we end up making decisions based on empty metrics. Tests that increase the percentage but don't detect errors or provide value.
Coverage shouldn't be a goal in itself, but rather a tool to reflect on what we haven't tested yet.
In the video I explain why chasing a number can make us lose focus, and what to do instead to make our metrics truly useful.Retry