The Impact of Test-Driven Development on Software Development Productivity — An Empirical Study
Integrity signals
Registry
Cites
Statistics
Claims the paper makes
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?
This approach will lead to high test coverage, conjoined with the opportunity for autonomous cooperation of distributed teams as well as increased flexibility.
“This approach will also lead to high test coverage, conjoined with the opportunity for autonomous cooperation of distributed teams as well as increased flexibility [10].”
From Test Driven Development and Its Impact on Program Design and Software Quality: A Systematic Literature Review (2023) · cites this paper as [10]
Cites
Extreme Programming Explained: Embrace Change
Beck, K. L., & Andres, C. (2000) · Cited by 5,855 · see citing works
Kiczales, G. (1996) · ACM Computing Surveys · doi:10.1145/242224.242420 · Cited by 5,146 · see citing works
Bergmans, L., & Lopes, C. V. (1999) · Lecture notes in computer science · doi:10.1007/3-540-46589-8_17 · Cited by 2,951 · see citing works
Kiczales, G., Lamping, J., Mendhekar, A., Maeda, C., Lopes, C. V., Loingtier, J. M., & Irwin, J. (1997) · Lecture notes in computer science · doi:10.1007/bfb0053381 · Cited by 2,573 · see citing works
Experimentation in Software Engineering: An Introduction
Wohlin, C., Runeson, P., Höst, M., Ohlsson, M. C., Regnell, B., & Wesslén, A. (2011) · Lund University Publications (Lund University) · Cited by 2,214 · see citing works
Experimentation in Software Engineering
Wohlin, C., Runeson, P., Höst, M., Ohlsson, M. C., Regnell, B., & Wesslén, A. (2000) · Kluwer international series in software engineering · doi:10.1007/978-1-4615-4625-2 · Cited by 1,775 · see citing works
The Goal Question Metric Approach
Basili, V. R., Caldiera, G., & Rombach, H. D. (1994) · Cited by 1,587 · see citing works
Test-Driven Development by Example
Beck, K. L. (2002) · Cited by 1,457 · see citing works
Test Driven Development: By Example
Beck (2002) · Addison-Wesley Longman Publishing Co., Inc. eBooks · Cited by 1,278 · see citing works
Encyclopedia of Software Engineering
(2002) · Wiley eBooks · doi:10.1002/0471028959 · Cited by 1,168 · see citing works
Extreme Programming Explained: Embrace Change (2nd Edition)
Beck, K. L., & Andres, C. (2004) · Addison-Wesley Professional eBooks · Cited by 934 · see citing works
Frontiers in Artificial Intelligence and Applications
Yadav, J., Shukla, S., Sharma, K., Soni, N., Agarwal, S., & Pathak, P. C. (2022) · International Conference on Computation, Automation and Knowledge Management (ICCAKM) · doi:10.1109/iccakm54721.2022.9990098 · Cited by 659 · see citing works
ECOOP'97 — Object-Oriented Programming
AkÅit, M., & Matsuoka, S. (1997) · Lecture notes in computer science · doi:10.1007/bfb0053371 · Cited by 525 · see citing works
On the effectiveness of the test-first approach to programming
Erdogmus, H., Morisio, M., & Torchiano, M. (2005) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2005.37 · Cited by 315 · see citing works
Aspect-Oriented Analysis and Design: The Theme Approach
Clarke, S., & Baniassad, E. (2005) · International Linear Collider · Cited by 260 · see citing works
Extreme Programming and Agile Processes in Software Engineering
Marchesi, M., & Succi, G. (2003) · Lecture notes in computer science · doi:10.1007/3-540-44870-5 · Cited by 209 · see citing works
A structured experiment of test-driven development
George, B., & Williams, L. A. (2003) · Information and Software Technology · doi:10.1016/j.infsof.2003.09.011 · Cited by 202 · see citing works
Test-driven development as a defect-reduction practice
Williams, L. A., Maximilien, E. M., & Vouk, M. A. (2005) · doi:10.1109/issre.2003.1251029 · Cited by 183 · see citing works
Assessing Test-Driven Development at IBM
Maximilien, E. M. (2003) · Cited by 178 · see citing works
Aspect-Oriented Analysis and Design
Clarke, S., & Baniassad, E. (2005) · Addison-Wesley Professional eBooks · Cited by 176 · see citing works
Experiment about test-first programming
Müller, M. M., & Hagner, O. (2002) · IEE Proceedings - Software · doi:10.1049/ip-sen:20020540 · Cited by 164 · see citing works
Benchmarking software development productivity
Maxwell, K. D., & Forselius, P. (2000) · IEEE Software · doi:10.1109/52.820015 · Cited by 162 · see citing works
An initial investigation of test driven development in industry
George, B., & Williams, L. A. (2003) · ACM Symposium on Applied Computing · doi:10.1145/952532.952753 · Cited by 154 · see citing works
Evaluating the efficacy of test-driven development
Bhat, T., & Nagappan, N. (2006) · doi:10.1145/1159733.1159787 · Cited by 142 · see citing works
Evaluating advantages of test driven development
Canfora, G., Cimitile, A., García, F. O., Piattini, M. G., & Visaggio, C. A. (2006) · International Symposium on Empirical Software Engineering · doi:10.1145/1159733.1159788 · Cited by 83 · see citing works
Experimental context classification
Höst, M., Wohlin, C., & Thelin, T. (2005) · Proceedings/Proceedings - International Conference on Software Engineering · doi:10.1145/1062455.1062539 · Cited by 76 · see citing works
A prototype empirical evaluation of test driven development
Geras, A., Smith, M. R., & Miller, J. (2004) · doi:10.1109/metrics.2004.2 · Cited by 65 · see citing works
Software engineering : evolution and emerging technologies
Zieliński, K., & Szmuc, T. (2005) · Cited by 55 · see citing works
Madeyski, L. (2005) · Cited by 42 · see citing works
Self-citationVerification of Process Conformance in Empirical Studies of Software Development
Sørumgård, S. (1997) · Cited by 36 · see citing works
A prototype empirical evaluation of test driven development
Geras, A., Smith, M. R., & Miller, J. (2004) · doi:10.1109/metric.2004.1357925 · Cited by 36 · see citing works
The Effect of Test-Driven Development on Program Code
Müller, M. (2006) · Lecture notes in computer science · doi:10.1007/11774129_10 · Cited by 11 · see citing works
Flagged first, then by citations
1 of the 33 references couldn’t be matched to a known paper.
Cited by
Sorted by citations
SEGRESS: Software Engineering Guidelines for REporting Secondary Studies
Kitchenham, B. A., Madeyski, L., & Budgen, D. (2022) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2022.3174092 · Cited by 190 · see citing works
“The issue of process conformance in the context of Test-Driven Development experiments was discussed, e.g., in [40] and [41].”
MethodSelf-citationThe Effects of Test-Driven Development on External Quality and Productivity: A Meta-Analysis
Rafique, Y., & Mišić, V. B. (2013) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2012.28 · Cited by 121 · see citing works
Considering rigor and relevance when evaluating test driven development: A systematic review
Munir, H., Moayyed, M., & Petersen, K. (2014) · Information and Software Technology · doi:10.1016/j.infsof.2014.01.002 · Cited by 104 · see citing works
Factors Limiting Industrial Adoption of Test Driven Development: A Systematic Review
Čaušević, A., Sundmark, D., & Punnekkat, S. (2011) · IEEE International Conference on Software Testing, Verification and Validation (ICST) · doi:10.1109/icst.2011.19 · Cited by 87 · see citing works
Bissi, W., Serra Seca Neto, A. G., & Emer, M. C. F. P. (2016) · Information and Software Technology · doi:10.1016/j.infsof.2016.02.004 · Cited by 76 · see citing works
Madeyski, L. (2009) · Information and Software Technology · doi:10.1016/j.infsof.2009.08.007 · Cited by 74 · see citing works
“Interestingly, the TF practice is characterized by the higher ratio of active development time (described as typing and producing a code) to passive development time (spent on reading the source code, looking for a bug etc.) [ 35 ].”
BackgroundMethodInfluentialSelf-citationTosun, A., Dieste, O., Fucci, D., Vegas, S., Turhan, B., Erdogmus, H., Santos, A., Oivo, M., Toro, K., Jarvinen, J., et al. (2017) · Empirical Software Engineering · doi:10.1007/s10664-016-9490-0 · Cited by 50 · see citing works
“If we measure only LOC as the output of the process tested, subjects who produce more LOC but of less quality could be considered more productive (Madeyski and Szala 2007); this is not desirable.”
Method(2011) · Cited by 40 · see citing works
Test-Driven Development - Still a Promising Approach?
Kollanus, S. (2010) · International Conference on the Quality of Information and Communications Technology (QUATIC) · doi:10.1109/quatic.2010.73 · Cited by 35 · see citing works
“In different studies, the used metric may be total development effort [9], lines of code per hour [ 31 ] or number of implemented user stories [5].”
BackgroundInfluentialOperational definition and automated inference of test-driven development with Zorro
Kou, H., Johnson, P. M., & Erdogmus, H. (2009) · Automated Software Engineering · doi:10.1007/s10515-009-0058-8 · Cited by 35 · see citing works
“In their evaluation of TDD vs. test-last development, Madeyski and Szala (2007) used a plugin for Eclipse in order to assess the subjects' compliance with the assigned development processes.”
MethodInfluentialEffects of Developer Experience on Learning and Applying Unit Test-Driven Development
Latorre, R. (2014) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2013.2295827 · Cited by 34 · see citing works
“In this time we included both active (described as typing and producing the code) and passive development time (spent on reading the source code, self-training, looking for a bug, etc.) [32].”
BackgroundMunir, H., Wnuk, K., Petersen, K., & Moayyed, M. (2014) · International Conference on Evaluation and Assessment in Software Engineering (EASE) · doi:10.1145/2601248.2601267 · Cited by 28 · see citing works
“However, the results of this study are found consistent with the previously performed experiments [13] [34] [14] [5] [35] [36] [37] [38] [39] [11] [19] [40] [41] revealing little or no significant difference in terms of internal code quality, external code quality and productivity.”
ResultAn approach to test-driven development of conceptual schemas
Tort, A., Olivé, A., & Sancho, M.-R. (2011) · Data & Knowledge Engineering · doi:10.1016/j.datak.2011.07.006 · Cited by 27 · see citing works
The effectiveness of test-driven development: an industrial case study
Dogša, T., & Batic, D. (2011) · Software Quality Journal · doi:10.1007/s11219-011-9130-2 · Cited by 25 · see citing works
Impact of pair programming on thoroughness and fault detection effectiveness of unit test suites
Madeyski, L. (2008) · Software Process Improvement and Practice · doi:10.1002/spip.382 · Cited by 24 · see citing works
Self-citationBesouro: A framework for exploring compliance rules in automatic TDD behavior assessment
Becker, K. E., Pedroso, B. D. S. C., Pimenta, M. S., & Jacobi, R. P. (2014) · Information and Software Technology · doi:10.1016/j.infsof.2014.06.003 · Cited by 20 · see citing works
Behavior Driven Development: Tools and Challenges
Lenka, R. K., Kumar, S., & Mamgain, S. (2018) · International Conference on Advances in Computing, Communication Control and Networking (ICAC3N) · doi:10.1109/icacccn.2018.8748595 · Cited by 20 · see citing works
Impact of process conformance on the effects of test-driven development
Fucci, D., Turhan, B., & Oivo, M. (2014) · Proceedings of the ... ACM-IEEE International Symposium on Empirical Software Engineering and Measurement/International Symposium on Empirical Software Engineering and Measurement · doi:10.1145/2652524.2652526 · Cited by 19 · see citing works
“Madeyski and Szala [27] conducted an experiment on TDD effectiveness.”
MethodInfluentialEffects of Test-Driven Development: A Comparative Analysis of Empirical Studies
Mäkinen, S., & Münch, J. (2014) · Lecture Notes in Business Information Processing · doi:10.1007/978-3-319-03602-1_10 · Cited by 18 · see citing works
“Madeyski and Szała 2010 [21] Industry/Academia x x”
BackgroundInfluentialErdogmus, H., Melnik, G., & Jeffries, R. (2010) · CRC Press eBooks · doi:10.1081/e-ese-120044180 · Cited by 15 · see citing works
Critical Issues on Test-Driven Development
Kollanus, S. (2011) · Lecture notes in computer science · doi:10.1007/978-3-642-21843-9_25 · Cited by 13 · see citing works
“experiment [24][27] [21][30][46][48] [41] Case studies [7][13][40][45][47] [52][56][61][63] [44]”
BackgroundInfluentialSoftware Engineering Needs Agile Experimentation: A New Practice and Supporting Tool
Madeyski, L., & Kawalerowicz, M. (2016) · Advances in intelligent systems and computing · doi:10.1007/978-3-319-43606-7_11 · Cited by 14 · see citing works
“This tool was called Activity Sensor and developed back in 2006 at Wroc law University of Technology.”
BackgroundSelf-citationTest-Driven Development (TDD) in Small Software Development Teams: Advantages and Challenges
Ramzan, H. A., Ramzan, S., & Kalsum, T. (2024) · International Conference on Advancements in Computational Sciences (ICACS) · doi:10.1109/icacs60934.2024.10473291 · Cited by 12 · see citing works
“There hasn't been a thorough examination of how TDD approaches fit with the unique dynamics of small software development teams in the available literature [5].”
BackgroundContinuous Test-Driven Development - A Novel Agile Software Development Practice and Supporting Tool
Madeyski, L., & Kawalerowicz, M. (2013) · International Conference on Evaluation of Novel Approaches to Software Engineering · doi:10.5220/0004587202600267 · Cited by 11 · see citing works
Self-citationHybrid model for evaluation of quality aware DevOps
Batra, P., & Jatain, A. (2021) · International Journal of Applied Science and Engineering · doi:10.6703/ijase.202106_18(2).013 · Cited by 10 · see citing works
Tosun, A., Dieste, Ó., Vegas, S., Pfahl, D., Rungi, K., & Juristo, N. (2019) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2019.2949811 · Cited by 9 · see citing works
Technical Debt Aware Estimations in Software Engineering: A Systematic Mapping Study
Klimczyk, P., & Madeyski, L. (2020) · e-Informatica Software Engineering Journal · doi:10.37190/e-inf200102 · Cited by 7 · see citing works
“A number of practices have become popular, e.g., Continuous Integration, TDD, Pair Programming, to ensure sufficient production code and tests quality (e.g., [5–7]) and software development productivity (e.g., [8]).”
BackgroundSelf-citationTowards Automated Test Practice Detection and Governance
Oberhauser, R. (2009) · International Conference on Advances in System Testing and Validation Lifecycle (VALID) · doi:10.1109/valid.2009.25 · Cited by 5 · see citing works
“[ 15 ] studied TDD compliance with an Eclipse plugin that records low-level developer activity.”
BackgroundReliability of systematic literature reviews on test-driven development
Uyaguari, F., Acuña, S. T., Castro, J. W., Dieste, Ó., & Juristo, N. (2025) · Information and Software Technology · doi:10.1016/j.infsof.2025.107762 · Cited by 3 · see citing works
Understanding the dynamics of test-driven development
Fucci, D. (2014) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/2591062.2591086 · Cited by 3 · see citing works
Agha, D., Sohail, R., Meghji, A. F., Qaboolio, R., & Bhatti, S. (2023) · VAWKUM Transactions on Computer Sciences · doi:10.21015/vtcs.v11i1.1494 · Cited by 3 · see citing works
Hypermedia-based software architecture enables Test-Driven Development
Post, A. R., Ho, N., Rasmussen, E., Post, I., Cho, A., Hofer, J., Maness, A. T., Parnell, T. J., & Nix, D. A. (2023) · JAMIA Open · doi:10.1093/jamiaopen/ooad089 · Cited by 2 · see citing works
“In TDD, shown in Figure 1, tests are written before developing a new feature and serve as computable feature specifications.”
BackgroundComunica Tupi - tradutor para língua indígena Tupi Mondé
Fausto, I. R. D. S., Leta, F. R., & Braz, R. M. M. (2024) · Caderno Pedagógico · doi:10.54033/cadpedv21n1-156 · Cited by 2 · see citing works
Munir, H., & Moayyed, M. (2012) · Diva portal (Dalarna University Library) · Cited by 2 · see citing works
Test-Driven Development: uma revisão sistemática
Benato, G. B., & Vilela, P. R. S. (2021) · Revista Brasileira de Computação Aplicada · doi:10.5335/rbca.v13i1.11154 · Cited by 2 · see citing works
Position on metrics for security in requirements engineering
Kundi, M., & Chitchyan, R. (2014) · doi:10.1109/ret.2014.6908676 · Cited by 1 · see citing works
Driving Software Quality and Structuring Work Through Test-Driven Development
Mäkinen, S. (2012) · Työväentutkimus Vuosikirja · Cited by 1 · see citing works
Does Treatment Adherence Impact Experiment Results in TDD?
Karac, I., Panach, J. I., Turhan, B., & Juristo, N. (2024) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2024.3497332 · Cited by 1 · see citing works
“Concerns about process conformance as a threat to validity have also been expressed in primary studies [24], [25], [26].”
Empirical studies on the impact of test-first programming
Madeyski, L. (2009) · Cited by 1 · see citing works
Self-citationReliable Embedded Systems Development
Deng, D. (2014) · Libraries and Cultural Resources (University of Calgary) · doi:10.11575/prism/27616 · Cited by 1 · see citing works
Improving Development Practices through Experimentation: An Industrial TDD Case
Santos, A., Spisak, J., Oivo, M., & Juristo, N. (2018) · Asia-Pacific Software Engineering Conference (APSEC) · doi:10.1109/apsec.2018.00061
Towards Automated Software Testing: Evaluating LLMs in Generating Effective Test Cases
Pehlke, M., Eudenbach, C., Graw, M., & Jansen, M. (2025) · Communications in computer and information science · doi:10.1007/978-3-031-95127-5_16
Using software changes to understand the test driven development process
Nelson, N., McDonald, H., McDonald, S., Metoyer, R., Dig, D., & Hilton, M. L. (2015)
- Authors
- Madeyski, L., & Szała, Ł.
- Affiliations
- Wrocław University of Science and Technology (PL)
- ORCID
- Madeyski, Lech
- Venue
- Lecture Notes in Computer Science
- Publisher
- Springer Berlin Heidelberg
- Published
- 2007-09-12
- Pages
- 200-211
- ISSN
- 0302-9743 (ISSN-L)
- 1611-3349
- OpenAlex
- W1481560017
- Cited by
- 46
- References
- 33
- Citations by year
- 2025: 2 · 2024: 3 · 2023: 2 · 2022: 1 · 2021: 4 · 2020: 1 · 2019: 1 · 2018: 2 · 2017: 1 · 2016: 3 · 2015: 1 · 2014: 9 · 2013: 2 · 2012: 2
- FWCI
- 1.70
- Type
- conference paper
- Language
- en
- Open access
- closed
- Locations
- Lecture notes in computer science (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Physical Sciences › Computer Science › Software › Software Testing and Debugging Techniques
- Keywords
- test-driven development, software productivity, Goal Question Metric, software development process
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
