The sixth installment of the popular “Automation for the people” series by Paul Duvall was recently published. The article provides an overview of the different types of developer tests along with examples that you can add to your build process and run continually using a Continuous Integration (CI) system.

Published by IBM developerWorks, the article covers the following:

* Running JUnit tests via Ant
* Executing longer running component tests using JUnit and DbUnit
* Determining which methods take too long to execute using JUnitPerf
* Running Web-based functional tests with Selenium
* Assessing code coverage with Cobertura
* Testing continually with CruiseControl

The key to improving the reliability of your software is to run tests whenever a change occurs. Continuous testing leverages the practice of Continuous Integration to ensure highly reliable code.

For more information, see “Automation for the people: Continuous testing”.