Cited by 10Software Engineering Techniques and PracticesSoftware Testing and Debugging TechniquesSoftware Engineering Research

A Literature Review on the Challenges of Applying Test-Driven Development in Software Engineering

Open access
Staegemann, Daniel, Volk, Matthias, Perera, Maneendra, Haertel, Christian, Pohl, Matthias, Daase, Christian, Turowski, Klaus·2022·Complex Systems Informatics and Modeling Quarterly

Abstract

Due to the ongoing trend of digitalization, the importance of software for today’s society is continuously increasing. Naturally, there is also a huge interest in improving its quality, which led to a highly active research community dedicated to this aim. Consequently, a plethora of propositions, tools, and methods emerged from the corresponding efforts. One of the approaches that have become highly prominent is the concept of test-driven development (TDD) that increases the quality of created software by restructuring the development process. However, such a big change to the followed procedures is usually also accompanied by major challenges that pose a risk for the achievement of the set targets. In order to find ways to overcome them, or at least to mitigate their impact, it is necessary to identify them and to subsequently raise awareness. Furthermore, since the effect of TDD on productivity and quality is already extensively researched, this work focuses only on issues besides these aspects. For this purpose, a literature review is presented that focuses on the challenges of TDD. In doing so, challenges that can be attributed to the three categories of people, software, and process are identified and potential avenues for future research are discussed.

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.7250/csimq.2022-31.02

Cites

32 of 32 references verified0 citation errors · 0 not checkable

Statistics

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • A 100% coverage indicates that the production code has been thoroughly tested, but this metric cannot ensure that the tests have been carried out correctly or that the system is free of defects.

    “A 100% coverage indicates that the production code has been thoroughly tested, but this metric cannot ensure that the tests have been carried out correctly or that the system is free of defects [24].”

    From Test Driven Development and Its Impact on Program Design and Software Quality: A Systematic Literature Review (2023) · cites this paper as [24]

    The Background section says greater test coverage improves the likelihood of detecting errors, and the Discussion section warns that tests may provide confidence rather than actively look for issues. These passages support the caution that coverage alone is not proof of effective testing, but the paper does not address 100% coverage specifically or say that it indicates production code has been thoroughly tested. The indexed copy provides no page numbers for these passages. (LLM, conf=0.76)

    Experimental — accuracy not yet measured

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Cites

Flagged first, then by citations

Research works printed but not linked: 7

  1. Williams, . M. Maximilien, and M. Vouk, " est-driven development as a defect-reduction practice," in Proceedings of the 14th ISSRE, Denver, Colorado, USA, 2003, pp. 34-45.
  2. W. K. A. aw, " earning ffective est Driven Development -Software Development Projects in an Energy Company," in Proceedings of the First International Conference on Software and Data Technologies, Setúbal, Portugal, pp. 159-164, 2006.
  3. M. Karlesky, G. Williams, W. Bereza, and M. Fletcher, "Mocking the Embedded World: Test-Driven Development, Continuous ntegration, and Design Patterns," in Embedded Systems Conference, San Jose, California, USA, 2007.
  4. J. Webster and R. . Watson, "Analyzing the Past to Prepare for the Future: Writing a iterature Review," MISQ, vol. 26, no. 2, pp. xiii-xxiii, 2002.
  5. J. Vom Brocke, A. Simons, B. Niehaves, K. Reimer, R. Plattfaut, and A. Cleven, "Reconstructing the Giant: On the mportance of Rigour in Documenting the iterature Search Process," in Proceedings of the ECIS 2009, Verona, Italy, 2009.
  6. autenschläger, " he Perception of est Driven Development in Computer Science -Outline for a Structured iterature Review," in Lecture Notes in Business Information Processing, Business Information Systems Workshops, W.
  7. D. Staegemann, M. Volk, E. Lautenschläger, M. Pohl, M. Abdallah, and K. urowski, "Applying est Driven Development in the Big Data Domain -Lessons from the iterature," in Proceedings of the 2021 International Conference on Information Technology (ICIT), Amman, Jordan, pp. 511-516, 2021. Available: https://doi.org/10.1109/ICIT52682.2021.9491728 · DOI · Paper page

Cited by

Sorted by citations

Authors
Staegemann, D., Volk, M., Perera, M., Haertel, C., Pohl, M., Daase, C., & Turowski, K.
Affiliations
Otto-von-Guericke-Universität Magdeburg (DE)
Venue
Complex Systems Informatics and Modeling Quarterly
Published
2022-07-29
Issue
31
Pages
18-28
ISSN
2255-9922 (ISSN-L)
OpenAlex
W4289885683
Cited by
10
References
32
Citations by year
2026: 1 · 2025: 2 · 2024: 3 · 2023: 4
FWCI
2.23
Type
journal article
Language
en
Open access
Locations
  • Complex Systems Informatics and Modeling Quarterly (publishedVersion, cc-by)
  • DOAJ (DOAJ: Directory of Open Access Journals) (submittedVersion, cc-by-sa)
  • ICT Role for Next Generation Universitie (Riga Technical University) (submittedVersion, cc-by)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Software › Software Testing and Debugging Techniques
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
Keywords
test-driven development, software quality, software development process, software engineering practices, software productivity

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review