Normal procedure for grading code in CS classes is as follows:
- Student submits code
- TA runs code against test file to see if it handles everything like it should
- (optional but important) TA modifies student code to fix bug, or modifies test file so student code breaks less badly, and thus gets a more precise grade than
broken
; go back to step 2 - TA calculates grade
The test files here are important, in that if you have stupid test files your students will inappropriately get perfect grades, but in the interests of expediency you don't want to spend a long time creating them. I banged mine out in ten minutes, tops.
The professor I TAed has just asked for the test files I used; apparently many of the students believe that I individually hand crafted these files so as to break their code specifically, and thus he would like to pass the test files on to the people teaching the course next quarter on the grounds that they must be pretty good.
Mwahahahaaaa...