Back in my undergrad software testing course, we were taught test coverage in the context of a control flow graph. I think most coverage measurements (at least

Back in my undergrad software testing course, we were taught test coverage in the context of a control flow graph. I think most coverage measurements (at least in the GitHub projects where I've seen a coverage badge) only refer to statement coverage where it checks if every node of the CFG is reached. It's one of the weakest forms of testing and will rarely reveal the more obscure bugs that edge/(simple, prime, complete) path coverage testing can reveal. I personally think the industry should stop using (node) coverage as some kind of golden metric.