Skip to content

Changes to already published exercises: consequences #35

@sealexan

Description

@sealexan

In 'old' access, pushing an update for an already existing exercise had these effects:

  • red banner at the top for all students who already tested/submitted
  • if the student would not re-submit until the deadline, then the last submission would be re-graded using the new tests upon the deadline

This would be better

  • When a change happens, the students should not immediately notice anything. (most changes are irrelevant for the students and do not directly affect their score, e.g. typos in the description etc.). That also means:

    • no red banner
    • no automatic re-grading
    • the best score of all submissions counts as usual
  • TAs/Admins should see in the task list some indication that an exercise had been changed after at least 1 student already submitted, like some specific icon indicating that the task has outdated submissions.

  • TAs/Admins should have a button 're-grade' for each individual task, which will have the following effects:

    • all outdated submissions are marked as outdated in the frontend
    • every outdated submissions is regraded and added to the student's submissions
    • the student's score is whatever best score they got across all regraded submissions
    • if another change and re-grading is performed, then all previously non-outdated-but-now-newly-outdated submissions are re-graded again.
  • TAs/Admins should have a separate button to reset the submission counter to a specific value (just like for individual students). When clicked, the submission counters of every student should be set to min(value_selected_by_TA, student_remaining_submissions). So for example

    • if a student had 2/5 submissions remaining and the submission counter is reset to 4, the student now has 4/5 submissions
    • if a student had 5/5 submissions remaining and the submission counter is reset to 4, the student still has 4/5 submissions

Semantically this means:

  • by default, students don't notice anything about updates
  • if a task is regraded, all (not previously outdated) submissions of a student are regraded and the best regraded submission counts
  • if submissions are regraded, students will see duplicates of all (not previously outdated) submissions in their history: the newly outdated ones and the regraded ones. The outdated submissions are otherwise unaffected, they just no longer count towards the score and are marked as 'outdated', but students can still see the old score, output and hints, etc.
  • regrading and resetting submission counters are 2 entirely separate, independent features

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions