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
GIMP is huge tool that I certainly haven't mastered, but it's so useful to have around.
I used it this week to convert images from obscure formats to common ones. It's a great swiss army knife and runs everywhere.
I've been playing with labels on my code blocks. Sometimes I have useful labels, other times it's just "Example 2".
It's also unclear exactly where I put the label: Inside the box? Outside?
Are there any docs sites that do this really well?
It's a small thing, but I'm much happier with --version in the latest version of difftastic.
It shows the release number and the commit date. This gives you a reproducible build with age info.
It also shows OS, arch and compiler, because those are useful in bug reports.


