Code Coverage Caveats
Too Long; Didn't Read
A relatively common <a href="https://hackernoon.com/tagged/criticism" target="_blank">criticism</a> of statement-level code coverage tests is that, even though all statements may have been executed (i.e. you have 100% statement coverage), you may not hit all possible<em> execution paths</em>. Understanding that in the abstract is one thing, but yesterday I came across a case where this was made very clear to me in a <a href="https://hackernoon.com/tagged/practical" target="_blank">practical</a> setting.