Dave Schweisguth in a Bottle

I’ve found measuring code coverage (the coverage of code by automated tests) to be well worth my while, ranking not too far below test-driven development and continuous deployment as a practice that a software project should have in place to make me and my team happy and productive. But that’s not a universal opinion. Many software engineers, even diligent automated testers and continuous deployers, are quick to dismiss coverage, and it’s probably the thing that I’ve had to set up myself most often when I join a project. So let’s go over why it’s a valuable practice.