Considering rigor and relevance when evaluating test driven development: A systematic review

  title={Considering rigor and relevance when evaluating test driven development: A systematic review},
  author={Hussan Munir and Misagh Moayyed and Kai Petersen},
  journal={Inf. Softw. Technol.},

Why Research on Test-Driven Development is Inconclusive?

This work studied the state of the art in TDD research published in top venues in the past decade, and analyzed the way these studies were set up to identify five categories of factors that directly impact the outcome of studies on TDD.

Reporting systematic reviews: Some lessons from a tertiary study

Effectiveness of TDD on unit testing practice

The aim of this study is to investigate the impact of test driven development approach compared to an incremental test last development (ITLD), on unit test case quality and the finding are different from previous studies performed at academic settings.

Grey Literature in Software Engineering: A Critical Review

The effectiveness of test-driven development approach on software projects: A multi-case study

The present study tried to report the results from a comparative multiple-case study of two software development projects where the effect of TDD within an industrial environment showed the TDD developers develop software code with a higher quality rate, and it results in increasing team productivity than NON_TDD developers.

On the Retainment of Test-driven Development: Results from a Longitudinal Cohort Study with Novice Developers

Test-Driven Development (TDD) is an approach to agile software development, which is claimed to boost both external quality of software products and developers’ productivity. The results about the

A longitudinal cohort study on the retainment of test-driven development

The use of TDD has a statistically significant effect neither on the external quality of software products nor on the developers' productivity, but it is observed that participants using TDD produced significantly more tests than those applying a non-TDD development process.



The Effects of Test-Driven Development on External Quality and Productivity: A Meta-Analysis

The results indicate that, in general, TDD has a small positive effect on quality but little to no discernible effect on productivity.

A method for evaluating rigor and industrial relevance of technology evaluations

The model is applied and validated in a comprehensive systematic literature review of evaluations of requirements engineering technologies published in software engineering journals and shows that the model can be applied to characterize evaluations in requirements engineering.

Mapping study completeness and reliability - a case study

This study used the results of a systematic mapping study to investigate how well mapping studies identify clusters of related studies and to what extent such clusters are complete.

Factors Limiting Industrial Adoption of Test Driven Development: A Systematic Review

A systematic literature review on empirical studies explicitly focusing on TDD as well as indirectly addressing TDD identified seven limiting factors viz., increased development time, insufficient TDD experience/knowledge, lack of upfront design, domain and tool specific issues, and legacy code.

Does Test-Driven Development Improve the Program Code? Alarming Results from a Comparative Case Study

A comparative case study of five small scale software development projects where the effect of TDD on program design was studied using both traditional and package level metrics reveals that an unwanted side effect can be that some parts of the code may deteriorate.

A prototype empirical evaluation of test driven development

An experiment was devised to investigate the distinction between test-driven development and traditional, test-last development from the perspective of developer productivity and software quality and indicates that while there is little or no difference in developer productivity in the two processes, there are differences in the frequency of unplanned test failures.