Measured Test-Driven Development: Using Measures to Monitor and Control the Unit Development
Y. Dubinsky & O. Hazzan
Journal of Computer Science, Volume 3, Issue 5, pp. 335–344 · doi.org/10.3844/jcssp.2007.335.344
Abstract
We analyze Test Driven Development (TDD) from cognitive and social perspectives. Based on our analysis, we suggest a technique for controlling and monitoring the TDD process by examining measures that relate to the size and complexity of both code and tests. We call this approach Measured TDD. The motivation for TDD arose from practitioners’ tendency to rush into code production, skipping the required testing needed to manufacture quality products. The motivation for Measured TDD is based on difficulties encountered by practitioners in applying TDD. Specifically, with the need to frequently refactor the unit, after every few test and code steps have been performed. We found that the suggested technique enables developers to gain better control over the development process.
Licence and reuse
Free to read. This article carries the publisher’s copyright, as printed on it: © 2007 Science Publications. It is free to read; ask us before reusing it.
How to reuse this articleResponses (0)
About this article
Dubinsky, Y. & Hazzan, O. (2007). Measured Test-Driven Development: Using Measures to Monitor and Control the Unit Development. Journal of Computer Science, 3(5), 335–344. https://doi.org/10.3844/jcssp.2007.335.344
- Licence
- © Science Publications
- Issue
- Volume 3, Issue 5
- Policies
- Editorial independenceUse of generative AIData availabilityAppeals and complaints
- Version
- Version of record
