Hacker News new | ask | show | jobs
by bennyelv 1839 days ago
I think most people, including the managers are aware of the problem you've highlighted. What's the solution?
1 comments

The solution is don't measure test coverage. Measure something you actually care about, like minutes of downtime.
Every time a bug is found I ask my team to write a unit test for it to prevent regression for that bug.

During peer review I encourage Engineers to verify that the actual business logic has been tested, for example calculations.

If done correctly, a low unit test coverage can actually be of more quality than enforcing an 80% threshold