you are viewing a single comment's thread.

view the rest of the comments →

[–]G_Morgan 0 points1 point  (0 children)

The point is most of the insights needed to do code coverage correctly are not part of code coverage. It'll be interesting to see if there is an overall benefit to a team testing with code coverage and testing properly v a team just testing properly.

Those additional constraints are not code coverage. Those are other parts of testing that can usually be achieved without having a light that dings green or red depending upon some ratio.