An experimental evaluation of test driven development vs. test-last development with industry professionals
(2014) EASE '14 Proceedings of the 18th International Conference on Evaluation and Assessment in Software Engineering- Abstract
- Test-Driven Development (TDD) is a software development approach where test cases are written before actual development of the code in iterative cycles. Context: TDD has gained attention of many software practitioners during the last decade since it has contributed several benefits to the software development process. However, empirical evidence of its dominance in terms of internal code quality, external code quality and productivity is fairly limited. Objective: The aim behind conducting this controlled experiment with professional Java developers is to see the impact of Test-Driven Development (TDD) on internal code quality, external code quality and productivity compared to Test-Last Development (TLD). Results: Experiment results... (More)
- Test-Driven Development (TDD) is a software development approach where test cases are written before actual development of the code in iterative cycles. Context: TDD has gained attention of many software practitioners during the last decade since it has contributed several benefits to the software development process. However, empirical evidence of its dominance in terms of internal code quality, external code quality and productivity is fairly limited. Objective: The aim behind conducting this controlled experiment with professional Java developers is to see the impact of Test-Driven Development (TDD) on internal code quality, external code quality and productivity compared to Test-Last Development (TLD). Results: Experiment results indicate that values found related to number of acceptance test cases passed, McCabe's Cyclomatic complexity, branch coverage, number of lines of code per person hours, number of user stories implemented per person hours are statistically insignificant. However, static code analysis results were found statistically significant in the favor of TDD. Moreover, the results of the survey 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. (Less)
Please use this url to cite or link to this publication:
https://lup.lub.lu.se/record/4697166
- author
- Munir, Hussan LU ; Wnuk, Krzysztof LU ; Petersen, Kai and Moayyed, Misagh
- organization
- publishing date
- 2014
- type
- Chapter in Book/Report/Conference proceeding
- publication status
- published
- subject
- host publication
- [Host publication title missing]
- editor
- Shepard, Martin
- conference name
- EASE '14 Proceedings of the 18th International Conference on Evaluation and Assessment in Software Engineering
- conference location
- London, United Kingdom
- conference dates
- 2014-05-13 - 2014-05-14
- external identifiers
-
- scopus:84905455469
- DOI
- 10.1145/2601248.2601267
- language
- English
- LU publication?
- yes
- id
- 03390ecf-7e88-44fb-b2ff-aedcc1968f83 (old id 4697166)
- date added to LUP
- 2016-04-04 14:17:29
- date last changed
- 2025-04-04 14:48:28
@inproceedings{03390ecf-7e88-44fb-b2ff-aedcc1968f83,
abstract = {{Test-Driven Development (TDD) is a software development approach where test cases are written before actual development of the code in iterative cycles. Context: TDD has gained attention of many software practitioners during the last decade since it has contributed several benefits to the software development process. However, empirical evidence of its dominance in terms of internal code quality, external code quality and productivity is fairly limited. Objective: The aim behind conducting this controlled experiment with professional Java developers is to see the impact of Test-Driven Development (TDD) on internal code quality, external code quality and productivity compared to Test-Last Development (TLD). Results: Experiment results indicate that values found related to number of acceptance test cases passed, McCabe's Cyclomatic complexity, branch coverage, number of lines of code per person hours, number of user stories implemented per person hours are statistically insignificant. However, static code analysis results were found statistically significant in the favor of TDD. Moreover, the results of the survey 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.}},
author = {{Munir, Hussan and Wnuk, Krzysztof and Petersen, Kai and Moayyed, Misagh}},
booktitle = {{[Host publication title missing]}},
editor = {{Shepard, Martin}},
language = {{eng}},
title = {{An experimental evaluation of test driven development vs. test-last development with industry professionals}},
url = {{http://dx.doi.org/10.1145/2601248.2601267}},
doi = {{10.1145/2601248.2601267}},
year = {{2014}},
}