Given coverage data, how would you build a tool to decide which untested parts of a codebase most need tests?
The best I can think of is using profile data to ensure hotspots are tested. Not sure if it's ideal though: top level code and well-exercised logic would be highlighted.
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.
