I’m wondering about protected paths during assignment creation. When setting up assignment I see that there should be something like it… but there ain’t.
Picture instead of 1k words:
So, my question is: what are protected paths (in context of assignment creation) and when / how to use them?
Must be something new they are adding and added the Protected Paths text at the top before adding the area/block to set them up. If I edit one of my assignments I set up for this semester several weeks ago I do not see that text on the same screen. If I go to add a new assignment I get the same screen you do.
Hi, I have the same problem. Do you know how to solve this problem?
When we launched autograding in March we were also working on a feature to protect file paths so students could not change them, but due to a number of reasons decided not to launch this. It looks like we forgot to update the corresponding header copy as well. Sorry for the confusion!
For now we don’t have the option for teachers to set up protected file paths, but we are looking to pick up this work in the future. If you have any thoughts or feedback you’d like to see when it comes to protected workflow files for autograding and assignments please let us know!
Am I correct in interpreting this as there (currently) being no way to prevent the students from either modifying the attached test-files or modifying a workflow to run test-files from another repo/location?
In that case I do not see how anyone can use this for autograding. Anything involving grading needs to be tamperproof. Autotesting - sure, no problem if they change anything then.
I think ideally the code running during grading tests should be located completely separated from the student repos.
The same tests can of course be located inside the student repos, so that they can test their implementations, but since these tests can be easily modified, they should not be used for grading