" would mean that students can first submit three times without a penalty, after which M圜ourses starts to add a penalty of 10% per incorrect submission. For more advanced exercises, one certainly should set up a penalty regime as this encourages students to rigorously test their own codes before submission. This is a good setting for very basic questions where students are practicing the very basics. This means that the students have unlimited attempts with no penalty. Marking/Penalty regime: Here we set Penalty regime to 0. Smaller questions are usually easier to manage and and they are typically easier for students to understand in an introductory course. (2) Or you can have a larger coding assignment, where you then use per-test grading and give fractional points. In other words, you can build CodeRunner quizzes in two ways: (1) You can have several shorter questions with All-or-nothing grading, each of which gives few points (or zero).
CODERUNNER COLUMN 80 CODE
For simple programs or functions, the code either works or not. It is possible to give per-test grades, but this probably makes sense only for relatively complex coding assignments. Marking/All-or-nothing: Here we check All-or-nothing grading, which means that the students only get points from their answer when all tests pass successfully. Coding questions make little sense if the students do not get proper feedback. This option can be used for more sophisticated testing of student answers.įeedback: Force show strongly recommended. It is very important that the students learn to use a proper code editor and learn to test their own code. But always make it clear for the students that they should write and test their answers in a separate code editor, not directly in the CodeRunner answer box. And for longer codes, a larger box might be helpful so that students can properly see their code before they submit it for checking. For a very short code of just few rows, you could make the box even smaller. This setting is explained in the Wiki pages dealing with more advanced questions.Īnswer box: You can set the number or rows in the student answer box. CodeRunner question typeĬustomization: Do not check any boxes. Here we will go through the very basic settings needed to set up a simple exercise.
The question type is well-documented and you can click the question mark symbols for context-based help. M圜ourses opens a new page Editing a CodeRunner question. Start by adding a new question in a Quiz or in a Question bank (if you are not familiar with Quizzes, please see Aalto M圜ourses Help). Let's see how simple CodeRunner questions are set up. The Show differences button is very helpful as it highlights the differences in the expected output and the output from the student. If the student submits an incorrect answer, the output looks as below. More complex tests are introduced in the other sections of the Wiki. There can be an arbitrary number of tests and they can be much more complex than just comparing simple outputs. The Expected column shows what kind of output CodeRunner expects and Got column shows what the student code prints. If the answer is correct, the output show in the figure below is printed. The server runs the code and tests and returns the results to M圜ourses. M圜ourses will submit the answer to a Jobe sandbox, which is a small cloud-based server. Then they paste the solution to the Answer box and click Check. The students write their answer in their favorite code editor (for example, Spyder). Here is how the simple exercise looks like inside a Quiz:
0 kommentar(er)
