A Quantitative Comparison of Test-First and Test-Last Code in an Industrial Project
This paper presents a comparison of test-first and test-last development approaches on a customer account management software of a telecommunication company. While the management had plans for initiating a process that enforces test-first development over test-last, they also had concerns about the tradeoffs. Therefore, an exploratory case study with quantitative analysis is carried out on a pilot project where the code metrics and estimated manual inspection efforts of both approaches are compared. Our results indicate no statistical difference between the two approaches in terms of design (CK) metrics. On the other hand, we observe that test-last development yields significantly simpler code in terms of cyclomatic complexity and less (though not significant) manual inspection effort. Hence, our initial results indicate no superiority of test-first over test-last development in the described industrial context.
KeywordsTest first Test last Code metrics Case study
Unable to display preview. Download preview PDF.
- 3.Kaufmann, R., Janzen, D.: Implications of Test-Driven Development A Pilot Study. In: 18th Annual ACM Conference on Object-Oriented Programming, Systems, Languages and Applications (OOPSLA 2003), pp. 298–299. ACM, New York (2003)Google Scholar
- 4.Madeyski, L.: Preliminary Analysis of the Effects of Pair Programming and Test-Driven Development on the External Code Quality. In: Zieliski, K., Szmuc, T. (eds.) Frontiers in Artificial Intelligence and Applications, vol. 130, pp. 113–123. IOS Press, Amsterdam (2005)Google Scholar
- 8.Vu, J.H., Frojd, N., Shenkel-Therolf, C., Janzen, D.S.: Evaluating Test-Driven Development in an Industry-Sponsored Capstone Project. In: Proceedings of the Sixth international Conference on information Technology: New Generations (ITNG 2009), vol. 00, pp. 229–234. IEEE Computer Society, Washington (2009)CrossRefGoogle Scholar