Does PDF to Quiz tailor practice to earlier weaknesses when a learner returns?
PDF to Quiz retained the learner’s history across sessions but did not use it to target weaker topics. Practice restarted the fixed 47-question quiz with a previously answered fuse question from the learner’s stronger area, rather than focusing on parallel circuits.
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.
Personalization survives a new sessionFailEvidence
We clicked the practice button on the quiz page to resume practice in the new session.
The tool's response has no text to quote: it is what the evidence under Proofs shows.
| ✗ | Expected: Each learner’s new-session practice must use retained history to target their own weaker topic, rather than serving the same fixed focus.Found: It retained 53% mastery from one attempt, then served question 1 of the full 47-question quiz: a previously answered fuse item from the learner’s stronger area. |
History survived, but practice had to respond to earlier weaknesses. One learner returned; the absence of personalization controls meant a second learner could not receive a different focus. The failure concerns the practice offered to this account.
Weaknesses are visible. The quiz page’s lists of top correct and incorrect answers make the learner’s weak areas visible.
Pro feedback is not targeting. The website describes the Pro plan’s personalized breakdown as feedback after a quiz; choosing the next session’s questions remains with the learner.
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 | The learner returns to the material later → | |
| 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.