Does PDF to Quiz steer practice toward a learner's weaker topic?
PDF to Quiz identified parallel circuits and meter placement as weak areas, then recommended the full original quiz rather than topic-directed practice. Its 47-question practice pool still included questions the learner had already answered correctly.
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 is based on this test case.
Practice follows the weaker topicFailEvidence
You have a basic idea of circuits, but this test shows a clear pattern: you need to strengthen your understanding of parallel circuits and the roles of ammeters and voltmeters.
Transcribed from Proof 3 · Screenshot
| ✗ | Expected: Practice should change with performance history, directing each learner toward their weaker topic rather than giving both learners the same topic focus.Found: The original quiz had 47 questions; practice offered all 47, with no topic selector and previously correct questions at positions 1 and 10. |
The product had to direct practice toward the weaker topic. Instead, it reshuffled mastered questions into practice. The quiz and practice both ran successfully with paid access to weakness feedback, so this was not an access restriction or an interrupted attempt.
Explanations of weak concepts. The quiz feedback explains current splitting between parallel branches, the voltage across each branch, and where ammeters and voltmeters belong.
Question-level progress. The quiz dashboard lists correct and incorrect answers by question, without grouping results by topic or concept.
Shorter random practice. The practice setup lets the learner reduce the question count from 47 for a shorter random selection from the same quiz.
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 test case's result says which one 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 test case's result 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 | Personalized Practice → | |
| Scenario | One topic is weaker than the others → | |
| Tool | PDF to Quiz → |
Global scenario definition → · Global capability definition → · PDF to Quiz 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.