[Feature:Autograding] Add regrade_by to autograding history#12006
[Feature:Autograding] Add regrade_by to autograding history#12006
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #12006 +/- ##
============================================
+ Coverage 21.66% 21.71% +0.04%
- Complexity 9528 9582 +54
============================================
Files 268 268
Lines 36398 36563 +165
Branches 475 475
============================================
+ Hits 7886 7938 +52
- Misses 28041 28154 +113
Partials 471 471
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
JManion32
left a comment
There was a problem hiding this comment.
I ran recreate_sample_courses on this PR and let the autograding queue run. This was the only error that occurred, and it looks unrelated:
|
I didn't test this, but do you also correctly handle (the original) regrade from the command line: And have we also tested vcs & team submissions (so many options to test). Please update your notes in the PR message about all of the different types of gradeable you have tested this on. Thanks! |
Why is this Change Important & Necessary?
Whenever we click regrade, we have no idea who the submission has been graded by. If we want to include students regrading, we should have an idea of who regraded the submission. Therefore, we should add this in the queue file, which adds it to the history file.
What is the New Behavior?
Adds the user who regrades into the queue and history file
What steps should a reviewer take to reproduce or test the bug or new feature?
Make sure that autograding does not break. I have tested team, vcs, and notebook submissions. I have also verified that the history with regrade_by is written to the file.
Automated Testing & Documentation
Unit tests are included. E2E tests would still have to be written.
Other information