AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
Graded 8 October 2026

Can Quizgecko help a teacher see what the class struggled with?

Quizgecko does not surface the class's shared weakness in the teacher report for this scenario. The class report shows 28 completed quiz sessions and a single 16% average score, while learner results show weaker parallel-circuit answers and stronger series-circuit answers. But the teacher-facing analytics view shows only 0% avg, 0 attempts rows with no question text, so the shared weakness is not surfaced there.

1 of 1 test case failed

Every test case in this scenario has a result.

Pass rate0%0 of 1 with a result
Coverage1 of 1test cases with a result
0PassNo test case passed.
1FailMissed at least one thing it was expected to do; the reason and proof are on the row.
0Not gradableEvery result here could be graded.
0UntestedEvery test case in this scenario has a result.
The pass rate is a summary. The evidence is the test case below: what we sent, what we checked, what the tool returned, and the proof.

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
What we sent
InputDocument (PDF)
Chapter opener naming series and parallel circuits
Open the PDF ↗
What the tool returned

The tool's reply is shown in the screenshots under Proofs.

Expected vs. Found
✗Expected: The report should match the attempts, show the weaker topic as weaker, and make that weakness visible without erasing it in an overall score.Found: The report did not match the attempts; it showed only 16% overall, and the question panels listed blank 0% avg, 0 attempts rows.
Supporting proof
Proof 1Screenshot
Quiz complete card showing 81% and 103 XP
Open original ↗
Proof 2Screenshot
Quiz complete card showing 81% and 1676 XP
Open original ↗
Proof 3Screenshot
Student results modal with attempts by date
Open original ↗
Proof 4Screenshot
Per-question list showing parallel errors and series correctness
Open original ↗
Proof 5Screenshot
Course report summary and student session table
Open original ↗
Proof 6Screenshot
Analytics tab with average score and blank question panels
Open original ↗
Proof 7Screen recording
Merged recording showing classes and analytics views
Key moments
Open original ↗
Why this result

The learner attempts showed weaker parallel-circuit answers and stronger series-circuit answers, but the teacher-facing report and analytics did not reflect that shared weakness. The report showed only an overall 16% average, and the question panels listed blank 0% avg, 0 attempts rows.

Also observed on this row

Old attempts lower average. The 16% average and 0% pass rate include earlier abandoned attempts from 1 and 3 October, so the overall score is not based only on the completed attempts.

Tested by anshika gupta · evidence dated 7 October 2026

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.

Software that produced the output
Quizgecko
Build or version
N/A — no visible version number found anywhere in the recordings (SaaS web app, no exposed version indicator)
Surface
Web app
Set up before the run
Multiple learners completed a valid quiz on separable topics, with recorded answers showing stronger performance on one topic and weaker performance on another. The teacher then opened the normal class results or reporting view.
Tested
7 October 2026 · anshika gupta

How this scenario is graded

How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.

How results are decided

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.

The rules
  • 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.

LevelNameScope
BenchmarkQuiz Generation →15 scenarios · 10 tools
CapabilityClass Reports →
ScenarioThe teacher checks what the class struggled with →
ToolQuizgecko →

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.

from the publication record
9 October 2026First publishedQuiz Generation v1

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.

This matches what I see

You run the same kind of test against your own setup and get the same behaviour.

Agree →
This does not match

Yours behaves differently. Tell us what you got, with a screenshot if you have one.

Disagree →
Point out an issue

Something here is wrong — a reference value, a transcription, a grade.

Report an issue →
Request a retest

On a newer build, a larger dataset, or your own setup.

Request a retest →
We have fixed this

Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.

Vendor notice →
Filed against this evidenceNothing yet. Challenges, counter-evidence and fix notices appear here with their outcome, and stay on the page after they are resolved.
Cite this result
aidemos.com/benchmarks/quiz-generation/results/quizgecko/class-struggle-report · 0 pass · 1 fail · coverage 1/1 · graded 2026-10-08

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.

Input · Document (PDF) ↗application/pdf · 265 KB
Proof 1 · Screenshot ↗image/png · 115 KB
Proof 2 · Screenshot ↗image/png · 118 KB
Proof 3 · Screenshot ↗image/png · 241 KB
Proof 4 · Screenshot ↗image/png · 334 KB
Proof 5 · Screenshot ↗image/png · 198 KB
Proof 6 · Screenshot ↗image/png · 212 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input · Document (PDF)220bc6e2dc7e6824ee5bb81ff8f24b17c234c2eb1463835468fdc77a602c3dff
Proof 1 · Screenshot21d556f6efa2c4b708fef218d06d1cd1f28b861e84e5608fba91ce27faa395cc
Proof 2 · Screenshot1f3f7647f688d026f9c9144b913d0962fa0f0d04cbc2c4c82bf55f6247ddcc14
Proof 3 · Screenshotc7685bafd2b735d4d2d2e256b29cd1ed94d2ed29210a70c9b7e211fe09a41983
Proof 4 · Screenshot9fe42546ed395379c58df80469b1bf801f4c010a7cee375ab1cd19f94ebe676e
Proof 5 · Screenshot7b411e43ff0e8ec8812c4189fda5de878877f81463356fb3dc94f8dfcf141ffe
Proof 6 · Screenshot190c8ad8a9b45a6d257f298b7ee5ba1975b8311a6756712003030feb711d74cf
Proof 7 · Screen recordingcb8336c7b0bf7dd03535c4eeda2e138ea3b40c6e86c9beb7af0dfed4bf1f6bfa