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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |