While a formal "marking scheme" is normally not needed for public tests as no handmarking of these tests will be done, there can still be a scheme provided containing courtesy information. A sample would be just the following text:
This autotesting is provided to help you verify that the functions you write take the proper number of parameters and in some trivial cases return the correct values. This is not intended to provide a thorough test of your code, and the official marking suite will be more complete. Please be sure to continue to write rigorous tests for your submission.
This emphasizes to the students the purpose of the public tests to discourage them from the mentality of "My code passes the public tests, therefore it works properly in all cases."
In courses using BitterSuite, this text should just be put in the body of the mark-scheme
file in the testing suite directory. If computeMarks
is called with the -n
flag for nroff
formatting, then formatting line wrapping will be handled automatically for you, and you have the option to include a centred header similar to the following:
.ad c .br ============================= .br Fall 2007 CS 135 Assignment 2 .br ============================= .br .ad l This autotesting is provided to help you verify that the functions you write take the proper number of parameters and in some trivial cases return the correct values. This is not intended to provide a thorough test of your code, and the official marking suite will be more complete. Please be sure to continue to write rigorous tests for your submission. .br