Exercises in an Exam
An exam can mix every exercise type Artemis supports. They share the navigation sidebar and the clock described under Take an Exam, and differ in how you work and how you submit.
Text, modeling and programming exercises all dock the problem statement to the right — above the editor on a small screen. The arrow at its top corner collapses it when you want the editor to fill the space, and dragging the divider resizes the panes.
Quiz Exercises
A quiz can contain multiple choice, short answer and drag-and-drop questions, all listed one below another. Scroll between them or use the question overview on the left, which jumps to a question when you select it.
The overview also tells you what you have answered: each question type has its own colour, and an answered question is shown differently from an unanswered one, so a glance is enough to find what you have skipped.
To submit, select another exercise in the navigation sidebar. Your work is also saved every 30 seconds.
Text Exercises
You type your answer in the editor, which counts your words and characters as you go.
Modeling Exercises
The elements available for your diagram type sit on the right of the editor; drag them into the canvas. Selecting a placed element lets you set its name, attributes and methods. To connect two elements, drag from the edge of one to the other and Artemis draws the connection.
Help explains the editor if you have not used it before, and the fullscreen control gives the diagram your whole screen.
File Upload Exercises
You attach the file your answer consists of — a scan, a drawing, a spreadsheet — and choose Upload. Nothing is submitted until you do: there is no Save for this type, and moving to another exercise in the sidebar does not submit an unuploaded file.
Programming Exercises
Depending on the exercise you may work in the browser, in your own editor, or either.
In the browser you get three panes: the file browser, the code editor and the instructions. The file browser shows the whole project and lets you add, rename and delete files and folders — which is worth doing carefully, since deleting a file the tests expect will fail the build. The editor marks the line where a compilation error occurred.
Refresh discards your unsaved editor changes and reloads the files from the last commit. Your editor changes are saved every 30 seconds.
Submit sends your code to be built and tested; the result area changes from having no result to building, and then to the result itself. Nothing is built until you submit.
Working in Your Own Editor
Code gives you the repository address, over HTTPS or over SSH if you have registered a public key. Clone it, open the project in your editor, work, then commit and push — pushing does what Submit does in the browser.
Limited Feedback
Your instructor may hide the test results during the exam. You then learn only whether your code compiled: a failed build means it did not, and a passing build means it compiled but says nothing about your score. Both are normal in an exam.
Submission Limits
An exercise may carry a submission policy, which decides what repeated submissions cost you:
- None — submit as often as you like.
- Lock Repository — there is a limit, and once you pass it the repository is locked and you cannot submit again.
- Submission Penalty — there is a limit, and each submission beyond it costs you points.
When an Exercise Changes Mid-Exam
If your instructor corrects a problem statement while you are working, you get a notification. You can then switch between the new statement and a view that highlights what changed, so you do not have to re-read the whole thing to find the correction.
