I find test coverage a useful thing to track, but I can't find a good metric.
"Coverage decreased by 10%" sounds bad. If you're deleting pointless code that has tests, it's good!
Perhaps total untested lines of code is better?
miniblog.
Related Posts
3
Test code is total: we require it to always terminate or it's a failure! It also typically has 100% line and branch coverage.
I feel way less nervous about refactoring tests, you can always just run them.
I don't care what your project's test coverage is, but the fact that you're measuring it is a great sign.
The examples coverage in Rust is exceptionally good. It's weird how few languages include an example in their stdlib docs for sorting.
