Advertisement

Productivity of Test Driven Development: A Controlled Experiment with Professionals

  • Gerardo Canfora
  • Aniello Cimitile
  • Felix Garcia
  • Mario Piattini
  • Corrado Aaron Visaggio
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4034)

Abstract

With the growing interest for Extreme Programming, test driven development (TDD) has been increasingly investigated, and several experiments have been executed with the aim of understanding if and when it is preferable to the traditional practice of testing the code after having written it (named TAC in the paper). However, the research concerning TDD is at its beginning and the body of knowledge is largely immature. This paper discusses an experiment carried out within a Spanish software company with the aim of comparing productivity in TDD and TAC.

Keywords

Software Engineer Additional Time Unit Testing Code Development Ciudad Real 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Beck, K.: Extreme Programming explained: Embrace change. Addison-Wesley, Reading (1999)Google Scholar
  2. 2.
    Edwards, S.: Using test-driven development in the classroom: Providing students with automatic, concrete feedback on performance. In: Proc. of the Int’l. Conference on Education and Information Systems: Technologies and Applications, EISTA 2003, Orlando, Florida, USA (2003)Google Scholar
  3. 3.
    Erdogmus, H., Morisio, M.: On the effectiveness of test-first approach to programming. IEEE Transactions on Software Engineering 3(1), 1–12 (2005)Google Scholar
  4. 4.
    George, B., Williams, L.: A structured experiment of test-driven development. Information and Software Technology 46(5), 337–342 (2004)CrossRefGoogle Scholar
  5. 5.
    Geras, A., Smith, M., Miller, J.: A Prototype Empirical Evaluation of Test Driven Development. In: Proc. of the 10th Inter’l. Symposium on Software Metrics (METRICS 2004), Sidney, Australia. IEEE CS, Los Alamitos (2004)Google Scholar
  6. 6.
    Muller, M., Hagner, O.: Experiment about Test-first programming. In: Proc. of Empirical Assessment in Software Engineering, Keele, UK (2002)Google Scholar
  7. 7.
    Pankur, M., Ciglaric, M., Trampus, M., Vidmar, T.: Towards empirical evaluation of test-driven development in a university environment. In: Proc. of EUROCON 2003. Computer as a Tool, Ljublijana, Slovenia. IEEE CS Press, Los Alamitos (2003)Google Scholar
  8. 8.
    Sjoberg, D., Anda, B., Arisholm, E., Dyba, T., Jorgensen, M., Karahasanovic, A., Koren, E., Vokác, M.: Conducting Realistic Experiments in Software Engineering. In: Proc. of the 2002 Int’l. Symposium on Empirical Software Engineering (ISESE 2002), Nara, Japan. IEEE CS Press, Los Alamitos (2002)Google Scholar
  9. 9.
    Williams, L., Maximilien, E., Vouk, M.: Test-driven development as a defect-reduction practice. In: Proc. of the 14th IEEE Int’l. Symposium on Software Reliability Engineering, Denver, Colorado, USA. IEEE CS Press, Los Alamitos (2003)Google Scholar
  10. 10.
    The ECLIPSE IDE, Available in: http://www.eclipse.org/
  11. 11.
    The JUnit Testing Framework, Available in: http://www.junit.org

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Gerardo Canfora
    • 1
  • Aniello Cimitile
    • 1
  • Felix Garcia
    • 2
  • Mario Piattini
    • 2
  • Corrado Aaron Visaggio
    • 1
  1. 1.RCOST- Research Centre on Software TechnologyUniversity of SannioItaly
  2. 2.ALARCOS Research Group- Information Systems and Technologies Department, UCLM-Soluziona Research and Development InstituteUniversity of Castilla-La Manch Paseo de la Universidad, 4Ciudad RealSpain

Personalised recommendations