-
Notifications
You must be signed in to change notification settings - Fork 69
Give instructors access to source code of autograding actions #20
Comments
Good news! You can absolutely change the workflow and autograding.json files manually and check them into your template repository. When checking in the autograding files, don't setup autograding in the assignment (if you do, it will overwrite the files in the template repo) and it should work as expected. |
Awesome! Is that new though? I tried toxdocthst and autograding didn't seem to get set up (the autograde report didn't seem to be visible in the classroom view). Would you like me to set up an example assignment and retest, maybe sending you some screenshots?
On May 12, 2020 12:01 p.m., Jeff Rafter <[email protected]> wrote:
Good news! You can absolutely change the workflow and autograding.json files manually and check them into your template repository. When checking in the autograding files, don't setup autograding in the assignment (if you do, it will overwrite the files in the template repo) and it should work as expected.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#20 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AACY6NCMFT3MWW4NSPUHAV3RRFXGLANCNFSM4M2QD53Q>.
|
That would be fantastic... though this wasn't an official feature it is something I very much think should work! |
Here's how I'm set up. Inside my repository, I have the following folders: My The main thing under the steps is the "autograder" step and maybe the "checkout" one. Then, inside If you want more than one test, just copy the one object and add it to the "tests" array and tell your test runner to run certain suites or tests or whatever. |
It would be very helpful if we could edit the autograding workflow yml and test json files directly. Reling on a slightly inflexible GUI in this situation is a bit odd; for one thing, it means we can't keep our grading schemas in version control (!)
The text was updated successfully, but these errors were encountered: