Software testing in the computer science curriculum -- a holistic approach
ACSE '00 Proceedings of the Australasian conference on Computing education
A gimmick to integrate software testing throughout the curriculum
SIGCSE '02 Proceedings of the 33rd SIGCSE technical symposium on Computer science education
Rethinking computer science education from a test-first perspective
OOPSLA '03 Companion of the 18th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Implications of test-driven development: a pilot study
OOPSLA '03 Companion of the 18th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
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
Test-driven development goes to school
Journal of Computing Sciences in Colleges
Testing across the curriculum: square one!
Journal of Computing Sciences in Colleges
Testing first: emphasizing testing in early programming courses
ITiCSE '05 Proceedings of the 10th annual SIGCSE conference on Innovation and technology in computer science education
A survey of evidence for test-driven development in academia
ACM SIGCSE Bulletin
The JavaFest: a collaborative learning technique for Java programming courses
Proceedings of the 6th international symposium on Principles and practice of programming in Java
Test-driven design for introductory OO programming
Proceedings of the 40th ACM technical symposium on Computer science education
Unit test support for Java via reflection and annotations
PPPJ '09 Proceedings of the 7th International Conference on Principles and Practice of Programming in Java
Test-first Java concurrency for the classroom
Proceedings of the 41st ACM technical symposium on Computer science education
Mutation analysis vs. code coverage in automated assessment of students' testing skills
Proceedings of the ACM international conference companion on Object oriented programming systems languages and applications companion
Practical parallel and concurrent programming
Proceedings of the 42nd ACM technical symposium on Computer science education
CodeWrite: supporting student-driven practice of java
Proceedings of the 42nd ACM technical symposium on Computer science education
Running students' software tests against each others' code: new life for an old "gimmick"
Proceedings of the 43rd ACM technical symposium on Computer Science Education
On teaching arrays with test-driven learning in WebIDE
Proceedings of the 17th ACM annual conference on Innovation and technology in computer science education
Exploring influences on student adherence to test-driven development
Proceedings of the 17th ACM annual conference on Innovation and technology in computer science education
Impacts of adaptive feedback on teaching test-driven development
Proceeding of the 44th ACM technical symposium on Computer science education
Toward practical mutation analysis for evaluating the quality of student-written software tests
Proceedings of the ninth annual international ACM conference on International computing education research
Effective and ineffective software testing behaviors by novice programmers
Proceedings of the ninth annual international ACM conference on International computing education research
A formative study of influences on student testing behaviors
Proceedings of the 45th ACM technical symposium on Computer science education
| Hi-index | 0.00 |
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.