Change status (Correct/Incorrect) of CodeRunner question in Summary of attempt

Re: Change status (Correct/Incorrect) of CodeRunner question in Summary of attempt

von Richard Lobb -
Anzahl Antworten: 0

Giving students some of the test cases up-front with a pre-check but then deferring final marking to the end of the assessment is an interesting way to mark. We've never tried it. I assume you'd move to a partial marking system, rather than all-or-nothing, for such questions?

To answer your original question: since CodeRunner 4.0.1 (available at since March 2021, earlier on github) there's a Hide check checkbox in the author-edit form. So I'm guessing you're running an earlier version, in which case you'd have to use the JavaScript hack described in this thread.

With that in place, you can safely set the Precheck mode to Examples or Selected to run a subset of the testcases on Precheck. If you're using the JavaScript hack, it's still possible for a suitably smart student to enable the check button and submit anyway, but such a student is probably also sufficiently smart to realise that their submission history will show exactly what they did and to infer the likely consequences.

I was perhaps a little rash to suggest the Precheck message could also display a warning that final testing may fail. We can do that with our in-house question types because we use combinator template graders and can customise messages that come before or after the result table. Unless you're doing something similar, the best you'll be able to do is write a special Precheck test case that explicitly prints that message, which will appear in both the Expected and Got columns of the result table. Not pretty, but workable? Or (easier) just explain to everyone in the class how Prechecks work and what a Status of Precheck results means when they're making their final submission.