ACM Home Page
Please provide us with feedback. Feedback
Evaluating advantages of test driven development: a controlled experiment with professionals
Full text PdfPdf (134 KB)
Source International Symposium on Empirical Software Engineering archive
Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering table of contents
Rio de Janeiro, Brazil
SESSION: Test-driven development table of contents
Pages: 364 - 371  
Year of Publication: 2006
ISBN:1-59593-218-6
Authors
Gerardo Canfora  Research Centre on Software Technology (RCOST), Benevento, Italy
Aniello Cimitile  Research Centre on Software Technology (RCOST), Benevento, Italy
Felix Garcia  University of Castilla-La-Mancha, Spain
Mario Piattini  University of Castilla-La-Mancha, Spain
Corrado Aaron Visaggio  Research Centre on Software Technology (RCOST), Benevento, Italy
Sponsors
ACM: Association for Computing Machinery
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 44,   Downloads (12 Months): 303,   Citation Count: 1
Additional Information:

abstract   references   cited by   index terms   review   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1159733.1159788
What is a DOI?

ABSTRACT

Test driven development (TDD) is gaining interest among practitioners and researchers: it promises to increase the quality of the code. Even if TDD is considered a development practice, it relies on the use of unit testing. For this reason, it could be an alternative to the testing after coding (TAC), which is the usual approach to run and execute unit tests after having written the code. We wondered which are the differences between the two practices, from the standpoint of quality and productivity. In order to answer our research question, we carried out an experiment in a Spanish Software House. The results suggest that TDD improves the unit testing but slows down the overall process.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
 
3
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'03), (Orlando, Florida, USA, 2003).
 
4
 
5
George, B. and Williams, L. A structured experiment of testdriven development. Information and Software Technology 46 (May 2004), pp.337--342.
 
6
 
7
 
8
 
9
Muller, M., and Hagner, O. Experiment about Test-first programming. In Proc. of Empirical Assessment in Software Engineering (EASE'02), (Keele, UK, 2002).
 
10
Pankur M., Ciglaric M., Trampus M. and Vidmar T. Towards empirical evaluation of test-driven development in a university environment. In EUROCON 2003. Computer as a Tool. The IEEE Region 8 , Volume: 2, (Ljublijana, Slovenia, 2003), IEEE CS Press, pp.83, 86.
 
11
 
12
 
13
 
14
The ECLIPSE IDE. Available in http://www.eclipse.org/
 
15
The JUnit Testing Framework. Available in http://www.junit.org.



REVIEW

"Andrew Brooks : Reviewer"

The results of a controlled experiment on test-driven development (TDD) with 28 software professionals are reported. In a counter-balanced experimental design, subjects tackled one assignment using TDD and another assignment using testing after co  more...

Collaborative Colleagues:
Gerardo Canfora: colleagues
Aniello Cimitile: colleagues
Felix Garcia: colleagues
Mario Piattini: colleagues
Corrado Aaron Visaggio: colleagues