This article is a continuation of a series of articles about Test-Driven Development (TDD) and Continuous Integration (CI). The past couple articles introduced you to test-driven development and the notion of developing a comprehensive test suite for your application. The primary benefit to using the test-driven development approach is that you can deploy an application with the confidence that it is well tested and will behave as you expect it to.

Furthermore, technologies like mocking frameworks make it possible to test aberrant conditions such as network and file system exceptions that might otherwise go unnoticed and take your application down in production. Finally, you can integrate the execution of your test suite into your build process and then quantify how exhaustive your test suite is by measuring your “test coverageâ€?. In addition to introducing test-driven development and its benefits, the last article suggested that you require test coverage reports from your development teams so that you know how well tested the application is before you deploy it to the environment you’re tasked with managing.

This article introduces Continuous Integration, describes its motivations, and reviews the benefits that a technical organization can derive from it. Read the rest of the article at about:virtualization.