The TRY system -or- how to avoid testing student programs
SIGCSE '89 Proceedings of the twentieth SIGCSE technical symposium on Computer science education
Automatic submission and administration of programming assignments
ACM SIGCSE Bulletin
A semi-automated approach to online assessment
Proceedings of the 5th annual SIGCSE/SIGCUE ITiCSEconference on Innovation and technology in computer science education
Automatic graders for programming classes
Communications of the ACM
Working group reports from ITiCSE on Innovation and technology in computer science education
First year programming: let all the flowers bloom
ACE '03 Proceedings of the fifth Australasian conference on Computing education - Volume 20
Teaching software testing: automatic grading meets test-first coding
OOPSLA '03 Companion of the 18th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Why students drop out CS1 course?
Proceedings of the second international workshop on Computing education research
Automatic test-based assessment of programming: A review
Journal on Educational Resources in Computing (JERIC)
Java interfaces in CS 1 textbooks
Companion to the 21st ACM SIGPLAN symposium on Object-oriented programming systems, languages, and applications
Interface-based programming assignments and automatic grading of java programs
Proceedings of the 12th annual SIGCSE conference on Innovation and technology in computer science education
Implications of integrating test-driven development into CS1/CS2 curricula
Proceedings of the 40th ACM technical symposium on Computer science education
Hi-index | 0.00 |
Grading code in large introductory programming classes is fraught with difficulties. In particular, students deviate from the required specification---and these deviations in turn break instructors' test code, delay feedback, hurt grades, and drive instructors to create oppressive homework policies. We present a system called SpecCheck for automatically generating tests that inform students of these deviations before they submit their homework. Our system inspects a instructor's reference implementation of a homework and produces tests to validate student code for interface conformance. It aids in conditioning code for faster grading but avoids the hazards introduced by some autograders. We present the tool and an experience report of its effectiveness in a large first-semester programming course.