An initial investigation of test driven development in industry

ABSTRACT

Test Driven Development (TDD) is a software development practice in which unit test cases are incrementally written prior to code implementation. In our research, we ran a set of structured experiments with 24 professional pair programmers. One group developed code using TDD while the other a waterfall-like approach. Both groups developed a small Java program. We found that the TDD developers produced higher quality code, which passed 18% more functional black box test cases. However, TDD developer pairs took 16% more time for development. A moderate correlation between time spent and the resulting quality was established upon analysis. It is conjectured that the resulting high quality of code written using the TDD practice may be due to the granularity of TDD, which may encourage more frequent and tighter verification and validation. Lastly, the programmers which followed a waterfall-like process often did not write the required automated test cases after completing their code, which might be indicative of the tendency among practitioners toward inadequate testing. This observation supports that TDD has the potential of increasing the level of testing in the industry as testing as an integral part of code development.

REFERENCES

• 1: Auer, K. and Miller, R., XP Applied: Addison-Wesley, 2001.
• 2: Kent Beck, Extreme programming explained: embrace change, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1999
• 3: Beck, Test Driven Development: By Example, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2002
• 4: Kent Beck, Aim, Fire, IEEE Software, v.18 n.5, p.87-89, September 2001 [doi>10.1109/52.951502]
• 5: Barry W. Boehm, Software Engineering Economics, Prentice Hall PTR, Upper Saddle River, NJ, 1981
• 6: Chaplin, D., "Test First Programming," TechZone, 2001.
• 7: Cornett, S., "Code Coverage Analysis," Bullseye Testing Technology 2002.
• 8: Elfriede Dustin , Jeff Rashka , John Paul, Automated software testing: introduction, management, and performance, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1999
• 9: Gelperin, D. and Hetzel, W., "Software Quality Engineering," presented at Fourth International Conference on Software Testing, Washington D.C., June 1987.
• 10: George, B., "Analysis and Quantification of Test Driven Development Approach," North Carolina State MS Thesis, 2002.
• 11: Ron E. Jeffries , Ann Anderson , Chet Hendrickson, Extreme Programming Installed, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2000
• 12: Jeffries, R. E., "Extreme Testing," presented at Software Testing and Quality Engineering, 1999.
• 13: Martin, C. R., Advanced Principles, Patterns and Process of Software Development: Prentice Hall, 2001, in press.
• 14: Muller, M. M. and Hagner, O., "Experiment about Test-first programming," presented at Empirical Assessment In Software Engineering EASE '02, Keele, April 2002.
• 15: Royce, W. W., "Managing the development of large software systems: concepts and techniques," presented at IEEE WESTCON, Los Angeles, CA, 1970.
• 16: Williams, L. A., The Collaborative Software Process. Salt Lake City, UT: Department of Computer Science, 2000.

INDEX TERMS

Keywords:
agile methodologies, extreme programming, software engineering, software experimentation, test driven development