A structured experiment of test-driven development

@article{George2004ASE,
  title={A structured experiment of test-driven development},
  author={Boby George and L. Williams},
  journal={Inf. Softw. Technol.},
  year={2004},
  volume={46},
  pages={337-342}
}
Abstract Test Driven Development (TDD) is a software development practice in which unit test cases are incrementally written prior to code implementation. [...] Key Result Statistical analysis of the results showed that a moderate statistical correlation existed between time spent and the resulting quality. Lastly, the programmers in the control group often did not write the required automated test cases after completing their code.Expand
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. Expand
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 theirExpand
Impact of test-driven development on productivity, code and tests: A controlled experiment
TLDR
The benefits of test-driven development compared to iterative test-last development are small and thus in practice relatively unimportant, although effects are positive. Expand
Evaluation of Test Driven Development
This thesis is about a development practice that will help to create clean code that works, called Test Driven Development. Test Driven Development (TDD) is part of the Extreme ProgrammingExpand
On the Influence of Test-Driven Development on Software Design
TLDR
Results from this study indicate that TDD can be an effective software design approach improving both code-centric aspects such as object decomposition, test coverage, and external quality, and developer-centric aspect including productivity and confidence. Expand
Preliminary Analysis of the Effects of Pair Programming and Test-Driven Development on the External Code Quality
  • L. Madeyski
  • Computer Science
  • Software Engineering: Evolution and Emerging Technologies
  • 2005
TLDR
The aims of the large experiment performed at Wroclaw University of Technology was to investigate the difference between test-driven development and the traditional, test-last develop-ment as well as pair programming and solo programming with respect to the external code quality. Expand
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. Expand
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. Expand
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. Expand
Prioritizing the creation of unit tests in legacy software systems
TLDR
This paper investigates the adaptation of TDD‐like practices for already‐implemented code, in particular legacy systems, and presents a TDM approach that assists software development and testing managers to use the limited resources they have for testing legacy systems efficiently. Expand
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 41 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. Expand
Analysis and Quantification of Test Driven Development Approach
TLDR
This thesis is concerned with a set of structured TDD experiments on very small programs with pair programmers, where both student and professional TDD developers appear to achieve higher code quality, as measured using functional black box testing. Expand
Assessing test-driven development at IBM
TLDR
A non-trivial software system based on a stable standard specification is built using a disciplined, rigorous unit testing and build approach based on the test-driven development (TDD) practice, which reduces the defect rate by about 50 percent. Expand
Extreme programming explained - embrace change
  • K. Beck
  • Computer Science, Engineering
  • 1990
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. Expand
Refactoring test code
TLDR
It is found that refactoring test code is different from refactored production code in two ways: there is a distinct set of bad smells involved, and improving test code involves additional test-specific refactorings. Expand
The Collaborative Software Process
Anecdotal and qualitative evidence from industry indicates that two programmers working side-by-side at one computer, collaborating on the same design, algorithm, code, or test, perform substantiallyExpand
The collaborative software process(sm)
Anecdotal and qualitative evidence from industry indicates that two programmers working side by side at one computer, collaborating on the same design, algorithm, code, or test, perform substantiallyExpand
Experiment about test-first programming
TLDR
It turns out that test-first does not accelerate the implementation, and the resulting programs are not more reliable, but test- first seems to support better program understanding. Expand
Program comprehension risks and opportunities in extreme programming
TLDR
This work analyzes five key XP practices in depth: pair programming, unit testing, refactoring, evolutionary design, and collaborative planning, and develops a process assessment framework for analyzing software processes from the comprehension and reverse engineering point of view. Expand
Program Comprehension Risks and Opportunities in Extreme Programming
TLDR
This paper analyzes five key XP practices in depth: pair programming, unit testing, refactoring, evolutionary design and collaborative planning, and discusses the role that comprehension and reverse engineering can play in software process design. Expand
...
1
2
3
4
5
...