Can Quizgecko show what a class struggled with?
Quizgecko does not surface the class's shared weakness in the teacher report. The class view shows 28 completed sessions and a 16% average, while the difficulty/ease panels have blank question rows; both learners' own results are 81% on 53 questions.
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.
The class report exposes the shared weaknessFailEvidence
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 7 · Screen recording · ▶ 0:30
| ✗ | Expected: The report should match the attempts, show the weaker topic as weaker, make that weakness visible, and not flatten or reverse it with an overall score.Found: The class view shows a 16% average, but the question panels are empty and do not show the weaker parallel-circuit questions; both learner drill-downs show 81% quizzes. |
It is Fail because the class report gives only an overall score and empty difficulty/ease panels instead of a question or topic breakdown, so the shared weakness is not visible.
Average includes old tries. The 16% average and 0% pass rate include older 0%, 8% and 42% attempts, not just the two finished quizzes.
Engagement stayed at zero. The analytics view also shows zero flashcard and AI chat activity, and the session table shows dashes in those columns.
Only one learner's row-by-row answer list is shown, so the other learner's detailed answers are not visible.
Older practice sessions are included in the class average, so that figure is not based only on the two finished quizzes.
The attempt list continues below the frame, so only nine rows are legible.
Only seven of the 53 answer rows are visible in this capture.
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 | Class Reports → | |
| Scenario | The teacher checks what the class struggled with → | |
| 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.