Small Steps Lead to Big Improvements in Java Code Quality

So continuous integration is an important part of one's development process and one is eager to include a code-coverage check as part of the automated builds, but which coverage-rate targets should the development team set? Seasoned supporters of code coverage suggest that one aims for 75 percent, 85 percent, or perhaps even 100 percent coverage rates. After measuring the baseline coverage rates for a project at my organization, the author realized the development team needed to set the sights much lower than those rate targets.