| A survey of evidence for test-driven development in academia |
| Full text |
Pdf
(409 KB)
|
Source
|
ACM SIGCSE Bulletin
archive
Volume 40 , Issue 2 (June 2008)
table of contents
REVIEWS: Reviewed papers
table of contents
Pages 97-101
Year of Publication: 2008
ISSN:0097-8418
|
|
Authors
|
|
Chetan Desai
|
California Polytechnic State University, San Luis Obispo, California
|
|
David Janzen
|
California Polytechnic State University, San Luis Obispo, California
|
|
Kyle Savage
|
California Polytechnic State University, San Luis Obispo, California
|
|
| Publisher |
|
| Bibliometrics |
Downloads (6 Weeks): 20, Downloads (12 Months): 228, Citation Count: 2
|
|
|
ABSTRACT
University professors traditionally struggle to incorporate software testing into their course curriculum. Worries include double-grading for correctness of both source and test code and finding time to teach testing as a topic. Test-driven development (TDD) has been suggested as a possible solution to improve student software testing skills and to realize the benefits of testing. According to most existing studies, TDD improves software quality and student productivity. This paper surveys the current state of TDD experiments conducted exclusively at universities. Similar surveys compare experiments in both the classroom and industry, but none have focused strictly on academia.
REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
| |
1
|
S. Ambler. Test-Driven Development is the Combination of Test First Development and Refactoring. Dr. Dobbs' Agile Newsletter, June 12, 2006.
|
 |
2
|
|
| |
3
|
|
| |
4
|
S. Edwards. Using Test-Driven Development in the Classroom: Providing Students with Automatic, Concrete Feedback on Performance. In Proc. Intl' Conf. on Education and Information Systems: Technologies and Applications (EISTA), August 2003.
|
 |
5
|
|
| |
6
|
|
| |
7
|
|
 |
8
|
|
| |
9
|
|
 |
10
|
|
| |
11
|
|
| |
12
|
|
 |
13
|
Reid Kaufmann , David Janzen, Implications of test-driven development: a pilot study, Companion of the 18th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications, October 26-30, 2003, Anaheim, CA, USA
[doi> 10.1145/949344.949421]
|
| |
14
|
|
| |
15
|
|
| |
16
|
L. Madeyski. Preliminary Analysis of the Effects of Pair Programming and Test-Driven Development on the External Code Quality. Software Engineering: Evolution and Emerging Technologies, 130:113--123, 2005.
|
 |
17
|
|
| |
18
|
M. Muller and O. Hagner. Experiment About Test-First Programming. IEEE Proc. Software, 149(5):131--136, October 2002.
|
| |
19
|
|
| |
20
|
M. Pancur, M. Ciglaric, M. Trampus, and T. Vidmar. Towards Empirical Evaluation of Test-Driven Development in a University Environment. In IEEE Region 8 Proc. EUROCON, volume 2, pages 83--86. IEEE Press, September 2003.
|
 |
21
|
Jaime Spacco , William Pugh, Helping students appreciate test-driven development (TDD), Companion to the 21st ACM SIGPLAN symposium on Object-oriented programming systems, languages, and applications, October 22-26, 2006, Portland, Oregon, USA
[doi> 10.1145/1176617.1176743]
|
| |
22
|
S. Yenduri and L. Perkins. Impact of Using Test-Driven Development: A Case Study. Software Engineering Research and Practice, pages 126--129, 2006.
|
|