Using Web-CAT

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 (approx 10 %) as well as how well your code does with mine (usually around 50%). Since I can't distribute my tests without overly influencing yours I use an online grader called WebCAT. Most of you will be familiar with it from ECE 1574, however note ** I require code to be uploaded to Canvas during submission**.

Each assignment has instructions on what files to submit to Webcat as a zip file. This must be a zip file with no parent directory included in the archive.

1. Login to WebCAT using your PID and password. You should be assigned to this course automatically. Let me know if not.
2. Upload your zip file using the web-form and submit it. Each program will have an assignment entry. To submit an assignment, just click on the submit button, browse to the file you want to upload, and confirm it contains the correct files.
3. Wait for the results. The file is uploaded and your submission is placed in a grading queue to be processed. After completion the result summary shows your score and any diagnostic output. This is split into two sections, the results of running your tests and the results of running my tests ("Estimate of Problem Coverage"). If one of my tests is failing there is a hint displayed as to why.

You are given a x/total score based on the number of my tests that pass with your code. I try to include informative error messages in my tests to give you an idea where to look. Sometimes my tests will not compile with your code, in which case WebCAT will report compiler errors.

When you are done you still submit your code through Canvas.

Some tips for effective use of WebCAT:

• do not 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. The feedback time is wayyyyyy to slow. Students regularly ignore this advice to their peril.

• 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.

• WebCAT response times can get slow around submission time. So plan ahead. "WebCAT was slow" will not get you additional time.