Outdated Submission

Each course that is offered by ACCESS is defined by meta-data (e.g., when is it available), exercises (e.g., due date), and tasks (e.g., a test suite that is used for the grading). Some of this information can easily be changed without any repercussions (e.g., an extension of the due date), however, some information might affect the grading. For example, a more precise task description or a new test case in the private test suite.

Student solutions will be graded on submit, if such a “breaking change” is performed after a submission, the submission gets marked as “outdated” and the affected student will see a warning in ACCESS. To make it possible to accomodate the changes, the submission count gets reset, which gives the student the chance to update the previous solution. The safest way is to reset the code to the template (which always points to the most up-to-date version), and start from there again. Of course, students can still access their old solutions, so it is easy to copy & paste their old solution, but they should make sure that they are not missing any changes in the provided files and especially whether their solution still satisfies the new public test suite.

If a student does not provide a new submission, the system will automatically re-submit the last (now outdated) submission after the deadline to use the latest private test suite for the grading.