A rubric marks it, line by line.
Your shot tastes sharp and sour. What went wrong, and what would you change?
You tied the sourness to the water leaving too soon and named the right lever. You didn’t say why a finer grind slows it down.
Nine question types, from multiple choice to essays, code and numeric answers. Six of them are checked by code and cannot be marked wrongly; the other three are graded against a rubric written before you saw the question.
A chat tells you “great answer!” every time. Here a written answer is marked against a rubric written first, code runs against real tests, and a speaking drill hears what actually came out of your mouth.
Your shot tastes sharp and sour. What went wrong, and what would you change?
You tied the sourness to the water leaving too soon and named the right lever. You didn’t say why a finer grind slows it down.
total() must refuse a negative price. Make all three cases pass.
1def total(prices):2 """Sum a cart."""3 if any(p < 0 for p in prices):4 raise ValueError("negative")5 return sum(prices)
At the ticket desk in Madrid. Say each one out loud.
¿Dónde está la estación de tren?
Where is the train station?
/ˈdon.de esˈta la es.taˈθjon de tren/
That’s the one: es-TÁ, “is”. Next phrase.
Recognition is the easiest thing to fake your way through, which is why a generator that only makes multiple choice can tell you almost nothing.
The two everyone generates. Worth having, and worth not over-using: they test recognition, which is the easiest thing to pass without knowing anything. Multi-select is markedly harder because you cannot eliminate.
Fill the gap in a sentence. Put five steps in the right sequence. Give a number, checked with a tolerance so 9.81 and 9.8 are both right. All three are objectively markable and none of them can be guessed from the options.
You write it in your own words and it is marked against a rubric that came with the question, point by point, with written feedback saying which part you missed. This is the type most quiz generators cannot do, because the marking is the hard half.
JavaScript, Python, SQL and HTML run in your own browser and pass or fail against real tests. Nothing is asked to judge whether your code looks right — it either produces the expected output or it does not.
A piece of work rather than an answer, assessed on stated criteria. What you use when the thing being learned only shows up at the scale of a whole task.
Generating a question is easy. Deciding honestly whether an answer was right, and saying why it was not, is the part that makes practice worth doing.
Multiple choice, multi-select, cloze, ordering, numeric and code are all checked by code, not by a model — against the recorded answer, the sequence, the tolerance, or the test suite. There is no judgement involved, so there is nothing to hallucinate.
A short answer, essay or project is generated together with the criteria it will be marked against, before you ever see the question. Marking then happens against that rubric rather than against a fresh opinion, which is what stops the same answer scoring differently twice.
"Incorrect" teaches nothing. Every marked answer comes back with which part was missing or mistaken, so the attempt is worth more than the score. This is the whole reason to answer a question rather than read the answer.
A question you missed is not just logged, it is scheduled — returned for review before the material decays, and more often than the things you got right. A quiz you take once and never see again is a measurement, not practice.
The six we hear most. The intro film answers most of them in a minute and a half.
Yes, within the same limits as the rest of the product: 12 fully-written lessons a month on the free plan, and the questions inside those lessons come with them at no extra cost. Answering, grading and review are never metered — you can retake a quiz as many times as you like, and every attempt is marked in full. Pro raises the writing allowance to 150 lessons a month.
Against a rubric that was generated with the question, not with the answer. The criteria exist before you attempt it, so grading is a comparison rather than an opinion formed on the spot — which is what keeps the same answer from scoring differently on two runs. You see the rubric after marking, along with which specific criteria you met and missed.
Yes. Upload a PDF, a slide deck, your notes or a transcript, and the questions are built from what those documents say rather than from general knowledge about the subject — which is the difference between a quiz that prepares you for your exam and one that prepares you for a similar exam somewhere else.
Yes — longer, mixed-type assessments over a whole section are one of the lesson formats, distinct from the short checks inside a single lesson. A section exam draws on everything up to that point rather than only the last thing you read, which is a much better predictor of whether you actually know the material.
You can publish a course and share it as a link that anyone can read without an account, which covers handing a quiz to a class or a colleague. There is no question-bank export to CSV or QTI today — if you need one for an LMS, say so; it is a reasonable thing to want and knowing who wants it is what decides whether it gets built.
As many as the lesson needs, which is usually three to eight, and the types are chosen by what the lesson teaches rather than by a quota. A lesson about a procedure gets ordering and a checklist; a lesson about two things people confuse gets discrimination questions; a lesson about a calculation gets numeric answers with tolerances. A fixed "five multiple choice per lesson" is the pattern this deliberately avoids.