Can Quizgecko show whether a learner is improving?
Quizgecko fails to show learner progress by topic in this scenario. The counts line up with the attempts, but the captured views stay at quiz or question level, so the improved topic never appears more positive and the weaker topic never appears as needing work.
1 of 1 test case failed
Every test case in this scenario has a result.
The test case
Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above counts this row.
Progress agrees with the attempts behind itFailEvidence
No typed message was sent in this test.
The tool's response has no text to quote: it is what the evidence under Proofs shows.
Proof 4 · Screen recording · ▶ 3:10–3:11; ▶ 3:15–3:23
| ✗ | Expected: Progress should match attempts, show improvement on one topic, keep the other topic needing work, and not claim mastery while weakness remains.Found: Counts match attempts, but the views stay generic, so the improved topic is not shown positively and the weaker topic is not shown as needing work; mastery is not claimed. |
It is a Fail because the product never shows learner progress by topic. Counts match attempts, but the improved topic is not shown positively and the weaker topic is not shown as needing work, so two required behaviours are missing.
Question-level analytics. The analytics tab lists difficult and easy questions by question, not by topic, with rows reading 0% average and 0 attempts.
Partial completion only. The learner card says the quiz ended before every question was answered and labels that state as partial results.
The documented Mastery Score view is not shown here.
This modal shows whole-quiz scores, not topic breakdowns.
This still does not show the Analytics tab's contents.
Only part of the results list is visible.
Only five quiz rows are visible here.
Configuration and setup
How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.
- Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
- Fail: at least one expected behaviour clearly didn't happen; the row says which and quotes the tool.
- Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the row says what's missing.
Where this sits in the benchmark
This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.
| Level | Name | Scope |
|---|---|---|
| Benchmark | Quiz Generation → | 15 scenarios · 10 tools |
| Capability | Learner Progress → | |
| Scenario | The learner checks whether they are improving → | |
| Tool | Quizgecko → |
Global scenario definition → · Global capability definition → · Quizgecko product page →
History of this result
What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.
Act on this result
Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.
Verify the proof files
These files support this result. Open a file to inspect the original evidence.
File fingerprints (SHA-256)
A fingerprint identifies the exact file used for this result.