Using code coverage tools can be helpful to find dead code or untested sections of your project, however, when used as a KPI it can do more harm than good.

Marc G Gauthier

Code coverage is often misused as a KPI, giving a false sense of security about test quality. It's easy to inflate coverage numbers without actually testing meaningful behavior — for example, by using ternary operators or running code without assertions. The real measure of a good test suite is its ability to catch bugs and prevent regressions, not a percentage on a dashboard. Coverage tools remain useful for finding untested sections or dead code, but treating coverage as a goal leads to gaming the metric rather than improving tests.

Code Coverage Is A Vanity Metric