MarkUs Blog

Since Gabriel, Mélanie, and Simon are focusing on the development of the same feature, they have decided to use a team evaluation scheme.

1) Flexible marking scheme feature completion: 30%

• An instructor can choose/change which marking scheme an assignment should graded with.
• An instructor can add/edit flexible criteria for an assignment.
• An instructor or TA can grade submission with the flexible marking scheme view.
• A student can consult his results with the flexible marking scheme view.

2) Automated testing: 20%

• Unit testing
  • Tool integration (ex : mocha)
  • Use of mocks to isolate units.
  • Code coverage (average of 85%)
  • Meaningful test cases
  • No test failure
• Functionality testing
  • Tool integration (ex : Selenium)
  • Meaningful test cases
  • No test failure
• Acceptance testing
  • Tool integration (ex : Cucumber)
  • Meaningful test cases (the most important acceptance criteria for each user story)
  • No test failure

3) Documentation: 20%

• The code should be documented
• The tasks for this feature should be split up into tickets with clear descriptions
• There should be a document posted under “MarkUs Component Descriptions” on the DrProject site that explains the current state of the feature, future plans, etc.
• There should be a short screencast of the feature posted on the DrProject site

4) Overall Process: 30%

• Blog posts, status reports, or review requests indicated steady progress throughout the term
• The new marking scheme respects the client’s request.
• Good programming practice (clear code, small methods, use of constants, OO architecture)
• Consulted with other team members about design/implementation decisions and/or helped other team members (eg. through blog posts, review requests etc.)
• Contribution to the existing tests.