Grading Boundaries Wrong in Supervisor View #98
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "97-grading-boundaries-wrong-in-suervisor-view"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes #97
The conversion table is consistent with 'Thesis Instructions'.
(Does not work on test servers due to issue with service.grading.url. :-( )
97: Grading Boundaries Wrong in Supervisor Viewto WIP: 97: Grading Boundaries Wrong in Supervisor ViewDeployed to https://scipro-97-grading-boundaries-wrong-in-suervisor-view.branch.dsv.su.se
WIP: 97: Grading Boundaries Wrong in Supervisor Viewto Grading Boundaries Wrong in Supervisor ViewNow that we have the grade limits in the database connected to the template (#14) the "from november 2024" panel should display its information based on that data rather than a hardcoded copy so that it keeps working in the future as the template changes.
GradingReportService
has a method to fetch the template based on the project that can be used to display the dynamic data.GradingReportService.getTemplate
returnsGradingReortTemplate
, which contains a Collection ofGradeLimit
. However, the current data model ofGradeLimit
has no upper limit of a grade. makes it harder to get grade A's upper limit.The
GradingReportTemplate
also contain a collection ofGradingCriterionTemplate
each of which has agetMaximumPoints
. Summing all those together gives you the upper point limit of the entire report.Grading Boundaries Wrong in Supervisor Viewto WIP: Grading Boundaries Wrong in Supervisor ViewWIP: Grading Boundaries Wrong in Supervisor Viewto Grading Boundaries Wrong in Supervisor ViewThere could have been a little better automated tests for checking the upper and lower limit based on a small
GradingReportTemplate
rather than passing in an empty one.@ -363,0 +385,4 @@
gradeLimit = new GradeLimit();
gradeLimit.setGrade("C");
gradeLimit.setLowerLimit(22);
gradeLimits.add(gradeLimit);
Extracting a method creating the
GradeLimit
here may have been justified.