This article is the second in a two-part series on Test-Driven Development (TDD). The first part presented an overview of TDD and its motivations. This reviews the idea of code coverage, how it ties into TDD and the benefits that we, as developers, derive from TDD.

My counterpart Eric Wright has begun a similar two-part series from the Ops perspective, with part I reviewing the movement to Infrastructure-as-Code as how to leverage configuration management systems (e.g. Puppet, Chef) to embrace Test-Driven Development from an Ops perspective.

Read the full article at about:virtualization