Evaluating the efficacy of test-driven development: industrial case studies

@inproceedings{Bhat2006EvaluatingTE,
  title={Evaluating the efficacy of test-driven development: industrial case studies},
  author={Thirumalesh Bhat and Nachiappan Nagappan},
  booktitle={ISESE '06},
  year={2006}
}
This paper discusses software development using the Test Driven Development (TDD) methodology in two different environments (Windows and MSN divisions) at Microsoft. In both these case studies we measure the various context, product and outcome measures to compare and evaluate the efficacy of TDD. We observed a significant increase in quality of the code (greater than two times) for projects developed using TDD compared to similar projects developed in the same organization in a non-TDD fashion… 
The effectiveness of test-driven development: an industrial case study
TLDR
The results indicate that the TDD developers produced higher quality code that is easier to maintain, although the productivity of the developers did observe a reduction in productivity.
Realizing quality improvement through test driven development: results and experiences of four industrial teams
TLDR
Case studies were conducted with three development teams at Microsoft and one at IBM that have adopted TDD and 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.
The Impact of Test-Driven Development on Software Development Productivity - An Empirical Study
TLDR
The study reveals that TDD may have positive impact on software development productivity, and is characterized by the higher ratio of active development time in total development time than test-last development approach.
An Experimental Evaluation of the Effectiveness and Efficiency of the Test Driven Development
  • Atul Gupta, P. Jalote
  • Business
    First International Symposium on Empirical Software Engineering and Measurement (ESEM 2007)
  • 2007
TLDR
The results suggest that TDD helps in reducing overall development effort and improving developer's productivity whereas the code quality seems to be affected by the actual testing efforts applied during a development-style.
An Experimental Evaluation of the Effectiveness and Efficiency of the Test Driven Development
TLDR
The results suggest that TDD helps in reducing overall development effort and improving developer's productivity whereas the code quality seems to be affected by the actual testing efforts applied during a development-style.
A Comparative Case Study on the Impact of Test-Driven Development on Program Design and Test Coverage
TLDR
The results show that the effect of TDD on program design was not as evident as expected, but the test coverage was significantly superior to iterative test-last development.
A Comparative Case Study on the Impact of Test-Driven Development on Program Design and Test Coverage
  • M. Siniaalto, P. Abrahamsson
  • Computer Science
    First International Symposium on Empirical Software Engineering and Measurement (ESEM 2007)
  • 2007
TLDR
The results show that the effect of TDD on program design was not as evident as expected, but the test coverage was significantly superior to iterative test-last development.
Cost-Effectiveness of test-driven development
Test-Driven Development (TDD) is a software development practice in which test cases are written before code implementation. ISM eCompany, who specializes in web solutions, is adapting their
Continuous Test-Driven Development - A Novel Agile Software Development Practice and Supporting Tool
TLDR
In this article, the CTDD practice and the tool that is intended to use to support and evaluate theCTDD practice in a real world software development project are described and described.
An experimental evaluation of test driven development vs. test-last development with industry professionals
TLDR
The results of the experiment revealed that the majority of developers in the experiment prefer TLD over TDD, given the lesser required level of learning curve as well as the minimum effort needed to understand and employ TLD compared to TDD.
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 27 REFERENCES
Test-driven development as a defect-reduction practice
TLDR
This case study found that the code developed using a test-driven development practice showed, during functional verification and regression tests, approximately 40% fewer defects than a baseline prior product developed in a more traditional fashion.
An initial investigation of test driven development in industry
TLDR
It is 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, which supports that TDD has the potential of increasing the level of testing in the industry.
A structured experiment of test-driven development
On the effectiveness of the test-first approach to programming
TLDR
It is found that test-first students on averagewrote more tests and, in turn, students who wrote more tests tended to be more productive, and the minimum quality increased linearly with the number of programmer tests, independent of the development strategy employed.
Three Problems Overcome With Behavioral Models Of The Software Development Process
  • B. Curtis
  • Computer Science
    11th International Conference on Software Engineering
  • 1989
TLDR
In some cases the software process is purported to begin with a stage called something like requirements development, or in some cases with the earlier step of a feasibility study.
Extreme programming evaluation framework for object-oriented languages -- version 1.1
TLDR
The Extreme Programming Evaluation Framework (XPEF) provides a benchmark measurement framework for researchers and practitioners to assess concretely the extent to which an organization has adopted XP practices and the result of this adoption.
Extreme programming explained - embrace change
TLDR
You may love XP, or you may hate it, but Extreme Programming Explained will force you to take a fresh look at how you develop software.
Case study: extreme programming in a university environment
TLDR
This paper provides some guidelines for those starting out with extreme programming and observations about the key practices of XP suggest it is difficult to implement XP without coaching.
Issues in using students in empirical studies in software engineering education
TLDR
The costs and benefits of empirical studies with students for these actors are discussed, which are different because of the actors' different goals, expectations, and constraints, which must be recognized to fully exploit empirical Studies with students.
Extreme Programming Explained
Extreme Programming (XP) was conceived and developed to address the specific needs of software development conducted by small teams in the face of vague and changing requirements. This new
...
1
2
3
...