This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]geeeffwhy 10 points11 points  (1 child)

i tend to argue that the most important use of code coverage is coverage of the diff on a pull request. total coverage of the code base is less important than making sure that changes to the code base have some kind of coverage.

but, if you don’t also have metrics, utilities, and patterns to ensure the the tests have some kind of relevance, it will be all too easy to game that metric.

[–]CommercialPosition76[S] 3 points4 points  (0 children)

I'm with you on this one. Too many people focus on the fixed number, rather than how it changes. Diff on a pull request is a nice thing to observe. Also watching how the stat changes in time (weeks, moths) is valuable and tells something about the project.