Exams are a collection of sections and you can configure how learners will move through these sections via options set in the YAML front-matter of the exam document. There are two types of navigation available:
The following configuration options are relevant for section navigation:
||Should the exam be progressive (
||If the exam is progressive, should the order of the sections be randomized?|
The relevant part of the YAML front-matter to set these settings is:
A section in an exam document starts with a level-one heading, i.e., lines starting with a single hash
#. The following R markdown document, for example has four sections: Introduction, Confidence Intervals, MLE, and Done!.
# Introduction and
# Confidence Intervals is considered the content of section Introduction.
Unless the exam is configured to show feedback immediately after the exam is submitted (i.e.,
feedback="immediately"), the last section, Done!, is treated differently from the rest. It is considered the “end” section, and you should use this section to let learners know they have finished the exam.
The “end” section is a dead end and hence does not have a submit button at the bottom. It is always displayed last, even if the exam is configured to randomized the section order.
feedback="immediately", an exam document must have at least two sections: at least one section with actual content and the “end” section.
In progressive exams, only a single section is displayed at any given time. To move on to the next section, learners must click the submit button at the bottom of the section. This will save all their answers and the next section will be displayed. The exam is considered finished when the last section is submitted (not counting the “end” section).
You can randomize the order in which a learner moves through the sections by setting the option
order="random". The “end” section will always be displayed last.
You can overwrite some settings for individual sections with
section_config() in a R code chunk with server-start context. You can change the label of the submit button, or fix the order of the section.
In the above example, you may want to have the section Introduction always in its original position (i.e., first) and use a different button label, e.g.,
#! context="server-start" section_config("Introduction", fix_order = TRUE, button_label = "Start exam")
For all-at-once exams, the section order cannot be randomized and is always as given in the exam document. Only the last section (not including the “end” section) will have a submit button. This submit button will submit answers to all questions across all sections and will mark the exam as finished.