Evaluating advantages of test driven development: a controlled experiment with professionals

Authors:
Gerardo Canfora;Aniello Cimitile;Felix Garcia;Mario Piattini;Corrado Aaron Visaggio
Affiliations:
Research Centre on Software Technology (RCOST), Benevento, Italy;Research Centre on Software Technology (RCOST), Benevento, Italy;University of Castilla-La-Mancha, Spain;University of Castilla-La-Mancha, Spain;Research Centre on Software Technology (RCOST), Benevento, Italy
Venue:
Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering
Year:
2006

Citing 9
Cited 15

Extreme programming explained: embrace change

Extreme programming explained: embrace change
Metrics for Small Projects: Experiences at the SED

IEEE Software
Conducting Realistic Experiments in Software Engineering

ISESE '02 Proceedings of the 2002 International Symposium on Empirical Software Engineering
Test-Driven Development as a Defect-Reduction Practice

ISSRE '03 Proceedings of the 14th International Symposium on Software Reliability Engineering
A Prototype Empirical Evaluation of Test Driven Development

METRICS '04 Proceedings of the Software Metrics, 10th International Symposium
Software Productivity Measurement Using Multiple Size Measures

IEEE Transactions on Software Engineering
On the Effectiveness of the Test-First Approach to Programming

IEEE Transactions on Software Engineering
An Empirical Analysis of Software Productivity over Time

METRICS '05 Proceedings of the 11th IEEE International Software Metrics Symposium
OO Metrics in Practice

IEEE Software

Guest Editors' Introduction: TDD--The Art of Fearless Programming

IEEE Software
The impact of Test-First programming on branch coverage and mutation score indicator of unit tests: An experiment

Information and Software Technology
On the effectiveness of unit test automation at Microsoft

ISSRE'09 Proceedings of the 20th IEEE international conference on software reliability engineering
Impact of test-driven development on productivity, code and tests: A controlled experiment

Information and Software Technology
A multiple comparative study of test-with development product changes and their effects on team speed and product quality

Empirical Software Engineering
Critical issues on test-driven development

PROFES'11 Proceedings of the 12th international conference on Product-focused software process improvement
Using spring Roo for the test-driven development of Web applications

Proceedings of the 27th Annual ACM Symposium on Applied Computing
An approach to test-driven development of conceptual schemas

Data & Knowledge Engineering
Exploring influences on student adherence to test-driven development

Proceedings of the 17th ACM annual conference on Innovation and technology in computer science education
Analyzing the understandability of Requirements Engineering languages for CSCW systems: A family of experiments

Information and Software Technology
The impact of test-driven development on software development productivity: an empirical study

EuroSPI'07 Proceedings of the 14th European conference on Software Process Improvement
Impacts of adaptive feedback on teaching test-driven development

Proceeding of the 44th ACM technical symposium on Computer science education
Test first programming, design by contract, and intriguing coursework: ingredients for increasing student engagement

Journal of Computing Sciences in Colleges
Effective and ineffective software testing behaviors by novice programmers

Proceedings of the ninth annual international ACM conference on International computing education research
Considering rigor and relevance when evaluating test driven development: A systematic review

Information and Software Technology

Quantified Score

Hi-index	0.00

Visualization

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.