Peer Testing [9 pts]

Gather functional and usability feedback from your peers

Be prepared to run a heuristic evaluation in your assigned sessions on your machine and participate in another team's evaluation.
On the day of the peer testing session, the instructor will post an assigned schedule of heuristic evaluations. Every student will run at least one evaluation and participate in at least one other team's evaluation. All sessions must give the same instructions and ask participants to do the same tasks.

The grade for the peer testing session is assigned to the student running the evaluation. Note that you must have the system running on your own machine rather than a teammate's machine.

Evaluation Rubric

Total marks possible: 9 points.

Criteria Exceeds Expectations
Meets Expectations
Below Expectations
No Submission
Preparedness
Is the session ready to go at the start of the assigned time? 		[3 pt] [2 pt] [1 pt] The student running the session was somewhat late. The student's machine was not prepared in time and had to run the evaluation on another machine. The student did not follow the guidelines for running a heuristic evaluation. [0 pt] It was too late to run an evaluation by the time the student showed up and got the system ready.
Evaluation Professionalism
 [3 pt] All identified issues are logged in the GitHub repository (show to TA/instructor). [2 pt] [1 pt] [0 pt] The student did not run an evaluation.
Participation Professionalism
 [3 pt] The student completed all the peer feedback questionnaires for the teams they evaluated. The comments were constructive, thoughtful, and made helpful suggestions for the other team(s). [2 pt] The student completed all the peer feedback questionnaires for the teams they evaluated. The comments were adequate. [1 pt] The student missed some of the peer feedback questionnaires for the teams they evaluated, or only completed them minimally. [0 pt] The student did not participate in another team's evaluation.