# What Makes a Good Fill in the Code Assessment?

## Description/Purpose

A Fill in the Code assessment contains a question stem and a partially completed code block, along with a variety of correct and incorrect code snippets that the learner must select to complete the code block correctly.

These assessments are aligned to a learning standard and test a learners understanding of that learning standard.

## Place in Content

Fill in the Code assessments are presented to a learner as part of "Practice Packs" that they can engage with on the web or on the mobile app. These packs contain a variety of assessments and review cards that are aligned with the learning standards from the lesson the learner most recently completed.

## Fields in Author

• Language: The language being covered by this quiz question.
• Learning Standard: The learning standard being assessed by this question. The learning standard is not visible to the learner..
• Prompt: The required text of the assessment.
• Code Block: The required code block with the blanks.
• Answer Options: Answer options include one or more correct code snippet(s) to fill in the blanks in the code block. At least one incorrect answer option is required for all assessments. Do not use code ticks () in answers, since these are already assumed to be code.
• Hints: Information for each answer space to be provided to learners as far as what should be filled into the blank.. The hint is associated with the blanks themselves, not necessarily which answer a learner selects.

## Quality Standards

### Content/Structure

• Each assessment is aligned with a single learning standard.
• Assessment is distinct in structure and content from other assessments aligned with the learning standard (i.e. there aren't cloned assessments with different values).

### Editorial

• All text is formatted using markdown that follows the markdown style guide
• Blanks (answer spaces) are indicated with the special markdown syntax __~blank~__`
• Your language is technically precise and unambiguous.
• The title of your assessment is appropriate and relevant to the content and formatted with title case.
• The words "assessment" or "question" are not in the title field.
• Do not reference the placement of blanks or answers in the prompt (i.e. "In the code below...") as the user interface is subject to change.
• Prompts and hints should be a single sentence in length.

### Pedagogy/Learner Experience

• Code blanks have an unambiguous correct fill. There cannot be multiple correct combinations of answers.
• Every question evaluates the learner's understanding of a learning standard (not just syntax).
• Use the same terminology and syntax as covered in the associated lesson(s).
• Assessments should not reference topics that learners would not be introduced to in the normal course of content ordering. For instance, do not reference an advanced topic (like class syntax) in an assessment associated with an introductory topic (like variable declaration). If there is ambiguity because of different content item ordering in different containers (for instance, a lesson used in a course and a skill path), it is best to err on the side of making an assessment as universal and closely scoped to the learning standard itself.