Lidor Wyssocky (yes the same as in my previous post) runs a Blog on Optimizing Software Development.
Lidor warns about using test coverage metrics as they may create the illusion you are doing well, when you are not.
Problem is that test coverage metrics are always related to what's in the code, the problem is that lots of bugs are caused by what is NOT in the code.
This reminds me of a fine compiler we used at the Nijmegen university some 20 years ago.
If a program compiled fine, the program would show the message:
"None of the errors found" …
