Add Exercises to an Exam

An exam is built from exercise groups rather than from exercises directly. Each group is one slot on the paper, and each slot can hold several alternatives, so that students do not all receive the same exam.

Exercise Groups

When Artemis generates the individual exams it draws one exercise at random from every group. Three groups holding two exercises each therefore produce a three-exercise exam in eight possible combinations.

A group is either Mandatory or Optional. Every mandatory group appears in every individual exam. Optional groups are only drawn on if there are more groups than the Number of exercises in exam set in the exam configuration — which is how you offer a choice of topics without lengthening the exam. Groups are mandatory by default; Edit group changes it later.

Exercise groups with alternative exercises

Each group lists its exercises as rows. Drag a row's handle to move it into another group — exercises have no manual order within a group — and use the row's overflow menu (…) for the remaining actions, including generating a variant with AI.

ℹ️

Information:

For an exam where everybody writes the same paper, give each group exactly one exercise.

Import Exercise Groups

Import Exercise Group copies groups out of an existing exam, in two steps.

First choose the exam to copy from. Select Exercise Groups opens it.

Step one: choose the source exam

Then choose what comes across. You can deselect individual exercises, and rename both the groups and the exercises — including the short name of a programming exercise, which together with its title has to be unique. Importing into the same course therefore always needs a rename first; Artemis checks uniqueness when you start the import and tells you which ones clash.

Step two: choose the exercises

ℹ️

Information:

Exercises arrive with the configuration they had. The import cannot change a submission policy or turn static code analysis on or off, so if you need a different setup, import that exercise into the group on its own and configure it there. Everything else can be edited after the import.

Add Exercises

Add Exercise at the foot of a group opens Manage Exercises. Its Create tab offers the five exercise types — Programming, Quiz, Modeling, Text and File Upload — and takes you to the creation form for the one you pick. Its Import tab offers the same five types and copies an existing exercise into the group; its search covers the courses and exams you hold at least editor rights in, and matches on exercise title, course title or exercise id.

Adding an exercise to a group

Text and modeling exercises can also carry example submissions with example assessments. Assessors work through those first, which is how a correction team arrives at the real submissions already agreed on what the exercise is worth.

Programming Exercises

Two settings on a programming exercise need attention in an exam.

Enable manual assessment decides whether your assessors can grade the submissions by hand at all. Leave it off and the assessment is whatever the tests produced.

Test visibility decides what a student learns while writing. Configure Grading on the exercise lets you set the Weight, Bonus multiplier and Bonus points of each test case, and its Visibility. In an exam the useful setting is After Release Date of Results: the test still runs and still scores, but the student sees neither its feedback nor its points until results are published. Artemis applies it to every test case of a programming exercise created inside an exam.

Test case configuration for an exam exercise

ℹ️

Information:

An imported exercise keeps the visibility it had in its source exercise, which is usually not what an exam wants. The import form has a Set test case visibility to After Release Date of Results option for exactly this.

Hiding every test leaves the student knowing only whether their code compiled, which is often what an exam wants. Controlling when the tests run is a separate question from when their results become visible, and it depends on the setup: with Integrated Code Lifecycle you give the build phase that runs the tests an After due date inclusion condition, described under Configure the Build. With Jenkins the exercise instead offers Rerun tests after due date, which runs the suite once over every submission after the date you set.