[CSUSB]>> [CNS]>> [CSE]>> [R J Botting]>> biba.php
Bibliographic Item (1.0)
- Hakan Erdogmus & Maurizio Morisio & Marco Torchiano
- On the Effectiveness of the Test-First Approach to Programming
- IEEE Trans Software Engineering V31n3(Mar 2005)pp226-237
- =EXPERIMENT TESTING AGILE TFD TDD
- Summarizes previous studies: test-first makes no difference or improves quality and may or may not improve productivity.
- This paper has a controlled experiment comparing test-first with test-last development of a series of user stories.
- Test-first programmers broke stories into a series of tests and added one test and then added code to make program pass test. Test last coded complete story and then carried out all tests.
- Experiment: 40PCs Java JUnit ECLIPSE CVS, 35 3rd year volunteer students, 11 dropped out.
- Quality measure via hidden acceptance tests.
- Productivity in terms of number of stories per unit time.
- Theories: Test-first may tend to increase the number of tests, the quality, and productivity. However more tests anyway may increase quality and productivity.
- My translation of their statistics results:
- quality >= 0.55 + tests/10. NOTE: not a linear equation but an inequality.
- More tests increase the minimum number of tests passed in the acceptance
- Other factors can improve quality as well as tests.
- productivity= 0.255 + 0.659 tests.
- Test-first programmers did more tests on average.
- Test-first programmers where more productive and produced the same quality code.
- 30% dropped out -- "morbidity"
Search for bibliographic items containing a matching string.
Search for a specific bibliographic item by name.
To see the complete bibliography (1Mb+) select:[Bibliography]