Test Coverage Insights
Achieving high test coverage, often exceeding 80-90%, is a hallmark of effective test-driven development. Increasing coverage post-factum can lead to significant challenges, particularly if the project lacks a modular structure. Relying on separate teams to add unit tests can dilute code quality and misalign expectations, ultimately undermining the benefits of a cohesive testing approach.In this clip
From this podcast
Software Engineering Radio - the podcast for professional software developers
SE-Radio Episode 324: Marc Hoffmann on Code Test Coverage Analysis and Tools
Related Questions
Do you happen to know other figures from other projects? So coverage figures so that our listeners can get a feeling of where they should aim at.
Are there any drawbacks associated with the tracking code coverage you mentioned about gaming the metrics, other things people should look out for?
It's not right now, as I said before, if you want to increase the test coverage after the effect, you lose a lot of benefits, like creating correct code from the beginning or creating proper APIs.