[jerrod]

Hey Jerrod here, CEO of Codecov. We live in coverage world every day and I agree that there is work to be done.

Fundamentally, no one ever said that coverage had to just be a binary of 0 or 1 as a "hit" line, though it is definitely the branding that code coverage has today.

As some others on this thread mentioned, how is something being tested should matter: - Unit vs. integration vs. end-to-end test vs. other testing - Flakiness of test (non-determinism) - Accuracy of test (E.g., mutation testion / fuzzing)

Also, What is being tested matters: - How important is this line? How is often is it actually being called in production? - Are their errors / exceptions on this line that we can see?

I do not believe that 100% coverage is the goal, nor should it be for all teams.

Do you have feedback here? I'd love to talk more about this.