Discover the benefits and limitations of code coverage as a helpful tool when practicing TDD, and learn how to effectively use it while avoiding common pitfalls.
What would you consider the lower-bar when it comes to TDD-based code coverage as per your average "target"? My quick research indicates at minimum 60-70%, but based on certain provisos/circumstances:
I would not put any number as a target. If you have less than ~80% there is a high chance that you either have a lot of effectively dead code (either not in use or you don't care about the features it represents) or important features are not covered by tests. But I'll always treat it as a signal, not a target.
What would you consider the lower-bar when it comes to TDD-based code coverage as per your average "target"? My quick research indicates at minimum 60-70%, but based on certain provisos/circumstances:
(https://softwareengineering.stackexchange.com/questions/1380/how-much-code-coverage-is-enough?newreg=9c47c195716c454f8ca80fef586dd260)
https://testing.googleblog.com/2020/08/code-coverage-best-practices.html
I would not put any number as a target. If you have less than ~80% there is a high chance that you either have a lot of effectively dead code (either not in use or you don't care about the features it represents) or important features are not covered by tests. But I'll always treat it as a signal, not a target.