Test-driven development (TDD) is a software development practice that has been used sporadically for decades. With this practice, a software engineer cycles minute-by-minute between writing failing unit tests and writing implementation code to pass those tests. Test-driven development has recently re-emerged as a critical enabling practice of agile software development methodologies. However, little empirical evidence supports or refutes the utility of this practice in an industrial context. Case studies were conducted with three development teams at Microsoft and one at IBM that have adopted TDD. The results of the case studies indicate that the pre-release defect density of the four products decreased between 40% and 90% relative to similar projects that did not use the TDD practice. Subjectively, the teams experienced a 15–35% increase in initial development time after adopting TDD.
This is a preview of subscription content, access via your institution.
Buy single article
Instant access to the full article PDF.
Tax calculation will be finalised during checkout.
Subscribe to journal
Immediate online access to all issues from 2019. Subscription will auto renew annually.
Tax calculation will be finalised during checkout.
IEEE (1988) IEEE Std 982.2-1988 IEEE guide for the use of IEEE standard dictionary of measures to produce reliable software. IEEE Computer Society, Washington, DC
Basili VR, Shull F et al (1999) Building knowledge through families of experiments. IEEE Trans Softw Eng 25(4):456–473
Beck K (2001) Aim, fire. IEEE Softw 18:87–89
Beck K (2003) Test driven development—by example. Addison-Wesley, Boston
Beck K (2005) Extreme programming explained: embrace change. Addison-Wesley, Reading, MA
Beck K, Fowler M (2001) Planning extreme programming. Addison-Wesley, Reading, MA
Bhat T, Nagappan N (2006) Evaluating the efficacy of test-driven development: industrial case studies. International Symposium on Empirical Software Engineering, Rio de Janeiro
Cockburn A (2001) Agile software development. Addison-Wesley Longman, Reading, MA
Curtis B (1989) Three problems overcome with behavioral models of the software development process (panel). In: Proceedings of the International Conference on Software Engineering, Pittsburgh, PA. ACM, Pittsburgh, PA
Erdogmus H, Williams L (2003) The economics of software development by pair programmers. Eng Econ 48(4):283–319
Erdogmus H, Morisio M, Torchiano M (2005) On the effectiveness of the test-first approach to programming. IEEE Trans Softw Eng 31(3):226–237
Fenton NE, Pfleeger SL (1998) Software metrics: a rigorous and practical approach. Cole Brooks, Pacific Grove, CA
Fenton N, Pfleeger SL et al (1994) Science and substance: a challenge to software engineers. IEEE Softw 11(4):86–95
Fowler M (2000) UML Distilled. Addison Wesley, Reading, MA
Gelperin D, Hetzel W (1987) Software quality engineering. In: Proceedings of the Fourth International Conference on Software Testing, Washington, DC, June
George B, Williams L (2003a) An initial investigation of test-driven development in industry. In: Proceedings of the ACM Symposium on Applied Computing, Melbourne, FL
George B, Williams L (2003b) A structured experiment of test-driven development. Inf Softw Technol (IST) 46(5):337–342
Harrison W (1997) N = 1: an alternative for empirical software engineering research? Empir Software Eng 2(1):7–10
Harrison W (2004) Propaganda and software development. IEEE Softw 21(5):5–7
Humphrey WS (1989) Managing the software process. Addison-Wesley, Reading, MA
Janzen D, Saiedian H (2006) On the influence of test-driven development on software design. In: Proceedings of the Conference on Software Engineering Education and Training, Turtle Bay, HI
Kitchenham B, Pickard L et al (1995) Case studies for method and tool evaluation. IEEE Softw 12(4):52–62
Larman C, Basili V (2003) A history of iterative and incremental development. IEEE Comput 36(6):47–56
Larus J, Ball T, Das M, Deline R, Fahndrich M, Pincus J, Rajamani S, Venkatapathy T (2004) Righting software. IEEE Softw 21(3):92–100
Müller MM, Hagner O (2002) Experiment about test-first programming. IEEE Proc Softw 149(5):131–136
Müller MM, Tichy WF (2001) Case study: extreme programming in a university environment. In: Proceedings of the 23rd International Conference on Software Engineering (ICSE2001)
Royce WW (1970) Managing the development of large software systems: concepts and techniques. IEEE WESTCON, Los Angeles, CA
Sjøberg D, Anda B et al. (2002) Conducting realistic experiments in software engineering. In: Proceedings of the International Symposium on Empirical Software Engineering, Nara, Japan. IEEE Computer Society, Washington, DC
Srivastava A, Thiagarajan J, Schertz C (2005) Efficient integration testing using dependency analysis. Technical report: MSR-TR-2005-94. Microsoft Research, Redmond, WA
Williams L, Maximilien EM et al. (2003) Test-driven development as a defect-reduction practice. In: Proceedings of the IEEE International Symposium on Software Reliability Engineering, Denver, CO. IEEE Computer Society, Washington, DC
Zelkowitz MV, Wallace DR (1998) Experimental models for validating technology. Computer 31(5):23–31
At IBM we would like to thank the Raleigh and Guadalajara development teams; in particular, Julio Sanchez of Guadalajara and Dale Heeks from the FVT team. At Microsoft we would like to thank the Windows, MSN, and DevDiv teams that participated in this study without whom this work would not have been possible and the agile development community at Microsoft for valuable feedback on earlier work. This work done by Dr. Williams was supported by the National Science Foundation under CAREER Grant Nos. 0346903.
Editor: Pankaj Jalote
About this article
Cite this article
Nagappan, N., Maximilien, E.M., Bhat, T. et al. Realizing quality improvement through test driven development: results and experiences of four industrial teams. Empir Software Eng 13, 289–302 (2008). https://doi.org/10.1007/s10664-008-9062-z
- Test driven development
- Empirical study
- Development time