Quizzes, scoring, and interactions
Four built-in question types cover the standard assessments, scoring flows to the LMS gradebook automatically, and when the built-ins run out, anything your assistant can build in the browser can become a graded question with the same tracking.
The built-in question types
- Multiple choice, with optional feedback per option, so a wrong answer can teach instead of just failing.
- Fill in the blank, accepting several correct spellings; case-insensitive unless you want otherwise.
- Matching: pair items across two columns, click or tap, with the right-hand side shuffled automatically.
- Sorting: drag and drop items into categories (or click to place, which also makes it keyboard-accessible).
These four are the starting point, not the limit: your assistant can build custom question types that score and report just like them (see below).
Quiz pages and inline practice
Questions work in two settings. On a quiz page they form a submitted assessment with a submit button, attempt limits, and a results screen. Standalone, they drop into any content page with their own check-and-retry. Either setting can be graded, counting toward the course score, or left as practice, which is the default.
Scoring, in plain terms
- Pass mark. Each course that judges pass/fail has a passing score (70% unless you change it). The course score, judged against it, is the average of the pages you mark as graded, quiz pages and pages of graded questions alike. Practice never counts.
- Weighting. Any question can count for more than its neighbours; the page score is the weighted percentage. Graded pages can be weighted against each other too, so a final exam can carry 75% of the course score.
- Required or optional. A graded page the learner skips counts as zero. Mark it optional, like a practice quiz, and it counts only once taken.
- Attempts and retries. Limit attempts or leave them open. Retries can reset the whole quiz or keep already-correct answers locked. Attempts carry across sessions, and the score kept is the best attempt, not the last.
- Feedback timing. Show feedback immediately per question, only after submission, or never (for formal exams).
- Gating. A quiz can block progress until passed, and a course can unlock pages one at a time.
In the LMS, each question reports as its own interaction, so instructors see which questions learners missed, not just the final score.
"Make the module 3 quiz graded with three attempts, count the scenario question double, and don't reveal feedback until after submission. Learners must pass it to reach module 4."
Beyond the built-ins
This is where Tessera separates from traditional tools. A custom interaction your assistant builds registers with the same scoring machinery as the built-ins: it's graded, persisted, and reported to the LMS identically. Drawing a line on a diagram, a branching scenario, a timed matching game, a simulation; if it runs in a browser, it can be a question.
The Road Sign Match demo is a fifteen-round timed game built exactly this way.
"Build a hotspot question using floor-plan.png: learners must click the two tripping hazards. Score it like a normal question and include it in the final quiz."