InfoQ

News

Book Excerpt: How to Improve your Continuous Testing

Posted by Deborah Hartmann on Jul 30, 2007 12:52 PM

Community
Agile
Topics
Delivering Quality,
Agile Techniques
Tags
JUnit,
TDD,
Testing,
DbUnit,
NUnit,
Selenium,
Continuous Integration,
Fit / Fitnesse,
TestNG
Continuous Integration (CI) is a basic Extreme Programming practice, but it has also become widely accepted as an essential part of any competent software development activity. Developers talk about a good CI process (which includes a thorough test suite) as a "safety net" that allows them to try things on their local machines without fear of breaking the app upon final integration. But as time passes, the process can become slow, and when teams bog down they tend to abandon their CI best practices, undermining the value of this important code quality tool. InfoQ provides some advice and examples to create or improve CI test suites, in a Chapter excerpt, from a new CI book.

This chapter comes from the book Continuous Integration: Improving Software Quality and Reducing Risk by Paul Duvall, Steve Matyas and Andrew Glover. The authors aim to help teams make this important practice a "non event" - something that happens unobtrusively and as a matter of course, as opposed to the painfully long build times some teams experience. Long builds and inadequate test suites tend to lead to developer shortcuts and frequent "red" (broken) builds, at which point it's impossible to judge code quality based on CI results. The final result of this scenario tends to be quality-related delays to deployment.

To improve CI build times and test suite maintainability, read the InfoQ exclusive excerpt: Chapter 6: Continuous Testing from the book Continuous Integration: Improving Software Quality and Reducing Risk.

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.

No comments

Reply

Exclusive Content

10 Ways to Screw Up with Scrum and XP

Henrik Kniberg talks about 10 possible reasons to fail while doing Scrum and XP. Maybe the team does not have a definition of what Done means to them, or they don't know what their velocity is.

Tips from a Top Sports Team Coach

This article outlines 9 principles Marc Lammers discovered while building the world’s best field hockey team, mapping them to software development practices.

SOA Governance: An Enterprise View

Michael Poulin explains the necessity for SOA governance to ensure an Enterprise SOA's success, relying on concepts from the OASIS SOA Reference Model and Reference Architecture.

Developing Portlets using JSF, Ajax, and Seam (Part 2 of 3)

This article covers setting up a RichFaces portlet using JBoss Portlet Container and JBoss Portlet Bridge, deploying a RichFaces portlet, and RichFaces capabilities.

Scalability Worst Practices

This article discusses scalability worst pratices including The Golden Hammer, Resource Abuse, Big Ball of Mud, Dependency Management, Timeouts, Hero Pattern, Not Automating, and Monitoring.

Do the Hustle

Obie Fernandez shares his experience selling consulting services for both Thoughtworks and Hashrocket and give tips how Ruby developers can work with clients.

Natural Laws of Software Development - Deriving Agile Practices

Jeffries and Hendrickson derive Agile practices from the natural laws of software development. They don't just say "Be Agile!", but they explain why Agile practices make perfect sense.

Jinesh Varia About Amazon Alexa Web Service's Architecture

Jinesh Varia talks about the architecture of one of Amazon's web services called Alexa. Jinesh explains how Amazon has reached scalability, performance and reduced costs for the Alexa service.