Helping students appreciate test-driven development (TDD)

ABSTRACT

Testing is an important part of the software development cycle that should be covered throughout the computer science curriculum. However, for students to truly learn the value of testing, they need to benefit from writing test cases for their own software.We report on our initial experiences teaching students to write test cases and evaluating student-written test suites, with an emphasis on our observation that, without proper incentive to write test cases early, many students will complete the programming assignment first and then add the build of their test cases afterwards. Based on these experiences, we propose new mechanisms to provide better incentives for students to write their test cases early.We also report on some of the limitations of code coverage as a tool for evaluating test suites, and finally conclude with a survey of related work on introducing testing into the undergraduate curriculum.

REFERENCES

• 1: Henrik Bærbak Christensen, Systematic testing should not be a topic in the computer science curriculum!, Proceedings of the 8th annual conference on Innovation and technology in computer science education, June 30-July 02, 2003, Thessaloniki, Greece
• 2: Stephen H. Edwards, Rethinking computer science education from a test-first perspective, 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.949390]
• 3: S. H. Edwards. Using test-driven development in the classroom: Providing students with automatic, concrete feedback on perfomance. 2003.
• 4: R. L. Glass. Persistent software errors. IEEE Trans. Software Eng., 7(2):162--168, 1981.
• 5: Michael H. Goldwasser, A gimmick to integrate software testing throughout the curriculum, Proceedings of the 33rd SIGCSE technical symposium on Computer science education, February 27-March 03, 2002, Cincinnati, Kentucky
• 6: Christopher G. Jones, Test-driven development goes to school, Journal of Computing Sciences in Colleges, v.20 n.1, p.220-231, October 2004
• 7: Edward L. Jones, Software testing in the computer science curriculum -- a holistic approach, Proceedings of the Australasian conference on Computing education, p.153-157, December 2000, Melbourne, Australia [doi>10.1145/359369.359392]
• 8: 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]
• 9: Chuck Leska, Testing across the curriculum: square one!, Journal of Computing Sciences in Colleges, v.19 n.5, p.163-169, May 2004
• 10: B. Marick. How to misuse code coverage. In International Conference and Exposition on Testing Computer Software, June 1999.
• 11: Will Marrero , Amber Settle, Testing first: emphasizing testing in early programming courses, Proceedings of the 10th annual SIGCSE conference on Innovation and technology in computer science education, June 27-29, 2005, Caparica, Portugal
• 12: M. Muller and O. Hagner. Experiment about test-first programming. Software, IEE Proceedings {see also Software Engineering, IEE Proceedings}, 149(5):131--136, 2002.

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.5 Testing and Debugging
          Subjects: Diagnostics

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.5 Testing and Debugging
          Subjects: Symbolic execution

Keywords:
computer science education, marmoset, tdd, test-driven development