4 ms·
Totally agree that code coverage is not a sufficient metric for quality, but it's still an interesting one. At my company we have this language that is not mai
by abricq 3y ago
Totally agree that code coverage is not a sufficient metric for quality, but it's still an interesting one.
At my company we have this language that is not mainstream (Oberon) and therefore there was no code-coverage reporting at all. I found this paper and realized it was super easy to write a minimal code-coverage analysis from our AST parser and code formatter (internal tools). Somehow it had never occured to me that it was this simple.
The transition from "no code coverage at all" to "seing which module is covered and which is not" was really insightful !
- pjmlp 3y agoAs someone that worked in projects with 100% guidelines for nice QA dashboards, eventually everyone games the system in large project, unit tests are written to cover all execution flows, not necessarly being actual tests. Thus every code refactoring becomes a pain, as the tests aren't really testing the expectations of a function call, rather ensuring every line of code is shown as being covered.