Implications of integrating test-driven development into CS1/CS2 curricula

ABSTRACT

Many academic and industry professionals have called for more testing in computer science curricula. Test-driven development (TDD) has been proposed as a solution to improve testing in academia. This paper demonstrates how TDD can be integrated into existing course materials without reducing topic coverage. Two controlled experiments were conducted in a CS1/CS2 course in Winter 2008. Following a test-driven learning approach, unit testing was introduced at the beginning of the course and reinforced through example. Results indicate that while student work loads may increase with the incorporation of TDD, students are able to successfully develop unit tests while learning to program.

References

1. E. Barriocanal, M. Urban, I. Cuevas, and P. Perez. An Experience in Integrating Automated Unit Testing Practices in an Introductory Programming Course. ACM SIGCSE Bulletin, 34(4):125--128, December 2002.
2. C. Desai, D. Janzen, and K. Savage. A survey of evidence for test-driven development in academia. ACM SIGCSE Bulletin, 40(2):97--101, 2008.
3. S. Edwards. Using Test-Driven Development in the Classroom: Providing Students with Automatic, Concrete Feedback on Performance. In Proc. Int'l Conf. on Education and Information Systems: Technologies and Applications (EISTA), August 2003.
4. S. Edwards. Using Software Testing to Move Students from Trial-and-Error to Reflection-in-Action. ACM SIGCSE Bulletin, 36(1):26--30, March 2004.
5. H. Erdogmus, M. Morisio, and M. Torchiano. On the Effectiveness of the Test-First Approach to Programming. IEE Trans. Software Eng., 31(3):226--237, March 2005.
6. D. Janzen and H. Saiedian. Test-Driven Development: Concepts, Taxonomy, and Future Direction. IEEE Computer, 38(9):43--50, September 2005.
7. D. Janzen and H. Saiedian. Test-Driven Learning: Intrinsic Integration of Testing into the CS/SE Curriculum. In Proc. 37th Technical Symposium on Computer Science Education (SIGCSE), pages 254--258, ACM, 2006.
8. D. Janzen and H. Saiedian. Test-Driven Learning in Early Programming Courses. In Proc. 38th Technical Symposium on Computer Science Education (SIGCSE), pages 532--536, ACM, 2008.
9. R. Jeffries and G. Melnik. TDD: The Art of Fearless Programming. IEEE Software, 24(3):24--30, May-June 2007.
10. K. Keefe, J. Sheard, and M. Dick. Adopting XP Practices for Teaching Object Oriented Programming. In Proc. 8th Australian Conf. Computing Education, volume 52, pages 91--100, 2006.
11. M. Müller and W. Tichy. Case Study: Extreme Programming in a University Environment. In Proc. 23th Int'l Conf. on Software Eng. (ICSE), pages 537--544, May 2001.
12. T. Shepard, M. Lamb, and D. Kelly. More Testing Should be Taught. Commun. ACM, 44(6):103--108, 2001.
13. S. Yenduri and L. Perkins. Impact of Using Test-Driven Development: A Case Study. Software Engineering Research and Practice, pages 126--129, 2006.

Index Terms

• Social and professional topics

  • Professional topics

    • Computing education

      • Computing education programs

        • Computer science education

• Software and its engineering

  • Software creation and management

    • Software development techniques

      • Object oriented development

      • Software prototyping

    • Software post-development issues

      • Software evolution

  • Software notations and tools

    • Development frameworks and environments

      • Object oriented frameworks