The following is a rough marking rubric. As many of the evaluations are subjective, the decision of the professor is final.
- Assignments are marked out of 30.
- 2 marks for appropriate ownership declaration (earnable even if incapable of running)
- 4 marks for user-written unit testing (i.e. beyond the provided tests)
- 6 marks for code quality, including appropriate use of classes/objects (i.e. not all in one class!) and functions (i.e. not passing everything around in a single object or map) (earnable even if incapable of running - up to +2 marks (i.e. 8 is possible))
- Marking is primarily based on results from unit tests
- 8 marks for properly formatting the output of the hands
- 4 marks for opening bids and 3 or 4 passes ending the bidding
- 4 marks for answering bids
- 2 marks for final bids
- 3 bonus marks for play method/function
- Up to 3 bonus marks for regularly committing code to fossil.
- Extraordinary assignments could result in as much as 35 marks being assigned.
- Any form of plagarism or cheating (e.g. modifying tests to conform to the actual code) will result in a severe reduction - possibly to a grade of 0.
The mark for each assignment, and possible comments from the marker will be in a file called Mark.txt in the fossil repository.
The marker will place this file in the top level directory for the assignment (the same place where the Ownership.txt file is placed).
An email will be sent when the grades have been uploaded.