3 ms·
> which were highlighted by incomplete coverage This is the single most important part of code coverage IMO: we don't care about what the tests cover, we care
by Izkata 7y ago
> which were highlighted by incomplete coverage
This is the single most important part of code coverage IMO: we don't care about what the tests cover, we care about what the humans never considered.
For this reason I'm a proponent of 100% coverage with a major caveat: Any code you explicitly decided not to test gets marked "no cover", so it doesn't count for or against the coverage score. This way branches that were accidentally missed really stand out, and we're not bogged down by having to test 100% of the code.
- P_I_Staker 7y agoGreat idea we'll just add // Unit Testing begin not covered // Unit Testing end not covered To the start and end of every file (or however it's done in your suite). Then we can leave early, go to the bar, and have a nice pint ;)