Untested code is broken code. So you need to learn how to write your own tests.
All programming assignments will have associated tests. Some of these you write, and some I write. A portion of your grade depends on both the quality and completeness of your tests as well as how well your code does with mine. Since I can't distribute my tests without overly influencing yours I use an online grader to give you feedback. The grader is provided as courtesy to you to give you the best feedback we can before you submit your code for final grading. Most of you will be familiar with WebCAT from ECE 1574. This is similar. An important note, even though the grader keeps your submissions, I require your code to be uploaded to Canvas as the official submission.
Each assignment has instructions on what files to submit to the grader and to Canvas (as a zip file). This must be a zip file with no parent directory included in the archive.
ECE2574Fall2017
.When you are done you still submit your code through Canvas.
Some tips for effective use of the grader:
only submit code that at least implements stubs for all required methods and functions, otherwise nothing will compile.
you must have at least some tests implemented before submitting, otherwise nothing will compile. There is no reason to submit unless you have at least a basic test implemented.
do not use it as your compiler, only submit code you know compiles and passes some of your tests.
if there is an unclear message, search Piazza to see if anyone else has encountered it, and if not post a question. This is by far the fastest way to get it resolved.
The grader response times can get slow around submission time. So plan ahead. "the grader was slow" will not get you additional time.