Adding Code Coverage Metrics and Unit Tests to a Mature Application


For me, the question of doing something is never just about how. It is always also about why. The motivations for doing something will always input into the how of doing something they will affect how much effort is put in, how much organisational buy-in you get, how much the other developers will back you up and participate, how much help you get from other stakeholders and what form of action is taken.
As such, this paper will examine why you might add code coverage metrics and unit tests to a mature application. It includes some myths of unit testing and examines the relationship between design, implementation and testing.

Full Text: