Test-driven development as a defect-reduction practice (2003)
| Venue: | In Proceedings of the 14th IEEE International Symposium on Software Reliability Engineering |
| Citations: | 30 - 3 self |
BibTeX
@INPROCEEDINGS{Williams03test-drivendevelopment,
author = {Laurie Williams and E. Michael Maximilien and Mladen Vouk},
title = {Test-driven development as a defect-reduction practice},
booktitle = {In Proceedings of the 14th IEEE International Symposium on Software Reliability Engineering},
year = {2003},
pages = {34--45},
publisher = {IEEE Computer Society}
}
Bookmark
 |
 |
 |
 |
 |
 |
OpenURL
Abstract
Test-driven development is a software development practice that has been used sporadically for decades. With this practice, test cases (preferably automated) are incrementally written before production code is implemented. Test-driven development has recently reemerged as a critical enabling practice of the Extreme Programming software development methodology. We ran a case study of this practice at IBM. In the process, a thorough suite of automated test cases was produced. In this case study, we found that the code developed using a test-driven development practice showed, during functional verification and regression tests, approximately 40 % fewer defects than a baseline prior product developed in a more traditional fashion. The productivity of the team was not impacted by the additional focus on producing automated test cases. This test suite will aid in future enhancements and maintenance of this code. The experiment and the results are discussed in detail. 1.
