[This is an updated version of a note that was first published to a Microsoft internal blog in November 2008] There are many opportunities to misuse code coverage (see Marick 1999 or Lamey 2010). Focusing solely on code coverage numbers can lead to some very bad behaviors, but it does not follow...

[This note was first published to a Microsoft internal blog in October 2008] It is common to include code coverage goals as key criteria for deciding if is time to exit various milestones in the software development cycle. This suggests that code coverage numbers must be providing value; why else...