Skip to main content Accessibility help
×
Hostname: page-component-76fb5796d-dfsvx Total loading time: 0 Render date: 2024-04-28T18:17:02.549Z Has data issue: false hasContentIssue false

22 - The Agile Test-Driven Methodology Experiment

Published online by Cambridge University Press:  26 October 2009

John Watkins
Affiliation:
IBM Software Group, UK
Lucjan Stapp
Affiliation:
Assistant Professor, Warsaw University of Technology,
Joanna Nowakowska
Affiliation:
Rodan Systems S.A.
Get access

Summary

SYNOPSIS

This case study describes a research project to determine the differences between one group of subjects following an agile testing method and another group of subjects following an ad hoc approach to testing. Results showed that the use of an agile approach improved defect detection by some 50% with just a 10% increase in test effort over the control group.

Introduction

My name is Lucjan Stapp and I work as an Assistant Professor at the Warsaw University of Technology. This case study describes research conducted at the Warsaw University of Technology, Faculty of Mathematics and Information Science, to determine the differences between one group employing an agile testing method and a control group using an ad hoc approach to testing.

Overview of the Testing Challenge

Agile approaches are often proposed as a solution to improving a number of characteristics of the testing process; typical improvements are claimed in speed and cost of testing, but many of these claims are only backed up by qualitative or anecdotal evidence.

This research was conducted to try to quantify the benefits of agile versus ad hoc testing approaches.

Teams and Exercises

To check the cost of using test-driven methodology, we have created two groups with the same knowledge of programming in Java:

  • the test group, later called the TDD team (using test-driven development [TDD] methodology), and

  • the control group, which, traditionally, does not have unit tests built in.

Both groups have made the same, rather simple applications (about 6 hours of coding for a three-person group).

Type
Chapter
Information
Agile Testing
How to Succeed in an Extreme Testing Environment
, pp. 180 - 183
Publisher: Cambridge University Press
Print publication year: 2009

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure coreplatform@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×