Assessments
Test cases
A program question is marked by running the student's program against the test cases you wrote.
The fields
| Field | What it is |
|---|---|
| Test Case Name | A name, so a failure says which case broke |
| Arguments | Command-line arguments given to the program |
| Standard Input | What the program reads when it runs |
| Expected Output | What it must produce to pass |
| Mark/Score | What this case is worth, with per-case marking on |
| Negative Mark/Score | Penalty for this case, with per-case marking on |
The last two appear only when the question has Score/Mark at test case level turned on.
All or nothing, or partial credit
By default a program question is all or nothing: every case must pass.
Turning on per-case marking gives each case its own marks, so a program that handles ordinary input but fails an edge case earns part of the marks.
The choice changes what the question measures. All or nothing asks whether the program is right. Per-case marks show how far each student got.
Limits are part of the question
The time and memory limits are not a safety net. A correct but slow program fails the case, which is either what you intended or a trap you did not mean to set.
They also stop a program that never finishes from running forever.
What next
What happens after students submit, and how results reach them.