Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check and apply max deduction for handgrading annotations #514

Merged
merged 3 commits into from
Apr 27, 2024

Conversation

broad-well
Copy link
Contributor

@broad-well broad-well commented Apr 24, 2024

This PR fixes #502. When an annotation is applied or deleted in the Handgrading interface, we compute the effective change to the score based on its max deduction and total number of applications so far.

Tests are included for both applying and deleting annotations across the max deduction boundary. Additional tests are included for cases where the max deduction of an annotation is not a multiple of its unit deduction, such as ("-3/-7 max"). This PR's implementation changes makes those tests pass.

This PR is a copy of #512, which had to be reopened to circumvent GitHub's erroneous stale review checks.

Replaced forceUpdate with expect(await wait_until(wrapper, w => !w.vm.saving)).toBe(true);
previously written test case Handgraders allowed to leave custom
comments
@james-perretta james-perretta merged commit 6c34143 into eecs-autograder:develop Apr 27, 2024
1 check passed
@james-perretta
Copy link
Contributor

Thanks again for this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Local score update when applying annotations past the max deduction is incorrect
3 participants