I don't know if this will be important to current TA's, but currently the TestGrader class has separate methods for getNotes and getScore, which leads to a lot of duplicate calculations being performed. These duplicates could be optimized by refactoring that to one method that returns some kind of object/record that has both the score and notes in it. This would also make reading the logic of that code easier without having to look between two methods to see essentially the same logic but spread out.
Note: Might want to wait on this until #643 is merged (or make it a dependent of the 398-code-coverage-grading branch)
I don't know if this will be important to current TA's, but currently the TestGrader class has separate methods for
getNotesandgetScore, which leads to a lot of duplicate calculations being performed. These duplicates could be optimized by refactoring that to one method that returns some kind of object/record that has both the score and notes in it. This would also make reading the logic of that code easier without having to look between two methods to see essentially the same logic but spread out.Note: Might want to wait on this until #643 is merged (or make it a dependent of the 398-code-coverage-grading branch)