A full mock tells you a student scored 58%. It rarely tells you why. Somewhere inside that 58% is a kid who can do moles but can’t do empirical formulae, and another who’s fine on empirical formulae but loses every mark on titration calculations — and the mock blurs them into the same number. By the time you’ve marked thirty scripts and pulled the threads apart, you’ve spent a weekend to learn something a six-question test could have told you on Tuesday.

That’s the case for topical IGCSE tests: short, granular checks that assess one sub-topic at a time. This guide is about building them well — how a topical test maker for Cambridge & Edexcel lets you create IGCSE tests from past-paper questions narrow enough to actually locate a gap, and how to use them formatively, week to week, instead of waiting for the big infrequent paper to tell you something’s wrong. It’s written for the individual IGCSE teacher running their own assessment, not a department.

Why micro-testing beats the big infrequent paper

A full mock is a summative instrument. It’s brilliant for predicted grades, exam-condition pace and pressure — and we’ve covered building one in minutes from past papers separately, because that’s a different job. What a mock is bad at is diagnosis. Three reasons:

• It aggregates. Twelve topics, one number. The signal you actually need — which sub-topic is failing — is averaged away the moment you total the marks.
• It’s too late. A mock six weeks into a unit catches the gap when the unit is already behind you. A topical test on Friday catches it while you can still reteach on Monday.
• It’s too rare. You run a couple of mocks a year. You can run a topical test every week, and frequency is what turns assessment from a verdict into a feedback loop.

Micro-testing flips all three. One sub-topic, one short test, marked fast enough that the data lands before the class moves on. You’re not measuring the student for a report — you’re finding the specific thing to fix next lesson.

What “one sub-topic at a time” actually means

The discipline here is narrowness, and it’s harder than it sounds. “Algebra” is not a sub-topic — it’s a syllabus strand. “Quadratics” is closer. “Solving quadratics by completing the square” is a sub-topic: a single, teachable, testable skill where a wrong answer points at one identifiable misconception.

The test is this: if a student fails the test, can you say in one sentence what to reteach? If the answer is “well, it depends which questions they got wrong,” your test is too broad — it’s a mini-mock wearing a topical label. Narrow it until a low score has a single, actionable meaning.

Practically, a good topical test is:

• 6–12 questions, not 40. Enough to be sure it wasn’t a fluke, short enough to sit in ten minutes.
• One sub-topic, one command-word range. Don’t mix “state” recall with “evaluate” extended response — pick the cognitive level you’re actually checking.
• Sittable inside a lesson. If it needs its own period, it’s not topical, it’s a paper.

How to build a tight topical test from past-paper questions

The fastest, most exam-honest way to assemble one is to pull real Cambridge or Edexcel past-paper questions filtered down to the sub-topic — which is exactly what a topical test maker is for. Building from the past-paper bank rather than authoring your own questions buys you three things for free: an examiner mark scheme attached to every question, exam-accurate command words, and calibrated difficulty. (That same “assemble, don’t author” principle is what makes exam-board-aligned tests trustworthy.)

Here’s the sequence:

1. Filter to the sub-topic, not the topic. Set board and subject, then drill the topic filter down to the narrowest level it offers — sub-topic, not just unit. This is the step that determines whether your test diagnoses or aggregates.
2. Pick one command-word band. If you’re checking whether they can recall the stages of mitosis, pull “state” and “describe” questions. If you’re checking whether they can apply it, pull “explain”. Mixing bands muddies what a wrong answer tells you.
3. Set a single difficulty, then add one stretch. Most questions at the level you’ve taught, plus one harder item to see who’s genuinely secure versus who’s just keeping up. Don’t build a test that’s all stretch — you’ll learn nothing about the middle of the class.
4. Keep it to 6–12 marks of focused work. Watch the running total. The moment it starts looking like a paper, cut it back.
5. Confirm every question carries its mark scheme. Pulled from a real past-paper bank, each question brings its examiner scheme — which is what lets the whole thing mark itself the second students submit.

That’s a diagnostic test built in a couple of minutes, every question real, every mark scheme attached, narrow enough that the result means something. If you want this in one place, Tutopiya’s free Test Builder filters real Cambridge & Edexcel past-paper questions by topic, sub-topic, difficulty and command word, so building the narrow test is the default rather than the effort.

Using topical tests formatively, week to week

A topical test only earns its keep if it changes what you do next. The rhythm that works:

• End-of-sub-topic check. The lesson you finish a sub-topic, run the test. Score before the next lesson, reteach the gap at the start of it. The loop is tight on purpose — the whole value is acting on the data before the class has moved on.
• Low stakes, high frequency. These aren’t graded events. Make them routine and ungraded so students answer honestly instead of revising for them, and so you can run them often without it becoming a marking burden. That only holds if marking is genuinely instant — which is the practical case for marking against the mark scheme automatically rather than by hand every Friday.
• Reissue the same test after reteaching. The cleanest evidence that your reteach worked is the same sub-topic test, sat again, with the scores moved. Same questions or fresh ones on the identical sub-topic — either way you’re measuring the fix, not a new topic.
• Assign it to the whole class in one go. Topical testing only scales if setting it takes seconds; the mechanics of assigning a quiz to a whole IGCSE class online are worth getting right once so the weekly habit costs you nothing.

The honest caution: don’t let “formative” become “constant testing with no follow-through”. A topical test you don’t act on is just a quiz. The reteach is the point; the test only tells you where to aim it.

Reading the data at sub-topic level

This is where micro-testing pays off and a mock can’t compete. Because the test is narrow, the data is too — and narrow data is actionable data.

• Per sub-topic, across the class. “Completing the square: 7 of 22 students under 50%” is a teaching instruction, not a statistic. That’s a whole-class reteach, scheduled. A mock would have buried those seven inside an algebra average that looked fine.
• Per student, across sub-topics. Run a few topical tests over a unit and a profile builds: this student is secure on everything except simultaneous equations. Now your intervention is one named skill for one named student — not “do some more algebra”.
• Trend after reteaching. The before-and-after on a reteach is the single most useful number you’ll get. It tells you whether the reteach landed, or whether the misconception is deeper than you thought and needs a different approach.

This is exactly what sub-topic-level analytics are for: a topic-by-topic class and per-student breakdown turns a pile of short tests into a map of who needs what. The Test Builder’s analytics report at that grain automatically, so you read the map instead of building it from a spreadsheet.

Topical tests vs full mocks: when to use which

Not a competition — they do different jobs, and you want both in rotation:

• Use a topical test when you’ve just taught a sub-topic and want to know, this week, whether it landed. Diagnostic, frequent, ungraded, narrow.
• Use a full mock when you need a predicted grade, exam-condition pace, and coverage across the whole spec. Summative, rare, graded, broad.

The mistake is using a mock for diagnosis (too late, too blurred) or a topical test for prediction (too narrow to grade off). Match the instrument to the question. Most teachers I work with run topical tests weekly through a unit, then one mock at the end to pull it all together under exam conditions — the topical data tells them what to reteach before the mock, so the mock score is higher and means more.

FAQ

What is a topical test maker for Cambridge & Edexcel? It’s a tool that lets you create IGCSE tests from past-paper questions filtered down to a single sub-topic — by topic, sub-topic, difficulty and command word — so you can build a short, focused test that assesses one skill at a time. Because the questions are real past-paper items, each comes with its examiner mark scheme attached, which is what lets the test auto-mark.

How is a topical test different from a mock? A mock is broad and summative — many topics, one aggregate score, used for predicted grades. A topical test is narrow and formative — one sub-topic, run frequently, used to diagnose a specific gap while you can still reteach it. A mock tells you a student scored 58%; a topical test tells you exactly which sub-topic cost them the marks.

How many questions should a topical IGCSE test have? Usually 6–12, sittable inside a single lesson. Enough to be confident the result isn’t a fluke, short enough to run weekly without becoming a marking burden. If it starts looking like a 40-mark paper, it’s drifted into mini-mock territory and lost its diagnostic edge.

How do I make sure the test is narrow enough to be useful? Apply one test: if a student fails, can you name in one sentence what to reteach? If yes, it’s narrow enough. If the answer depends on which questions they missed, drill your topic filter down to the sub-topic level and pick a single command-word band.

Can topical tests be marked automatically? Yes — when you create IGCSE tests from past-paper questions, each question carries its examiner mark scheme, so the test marks itself the moment students submit, with examiner-style feedback. That’s what makes weekly topical testing sustainable instead of a marking treadmill.

The bottom line

The big infrequent paper tells you something’s wrong long after you could have fixed it, and blurs what is wrong into an average. Short, granular topical IGCSE tests do the opposite: one sub-topic, built in minutes from real past-paper questions, marked instantly, read at the grain where the data is actually actionable. Run them week to week, act on what they show, and the gaps get caught and closed before the mock ever sees them.

Build your first topical test free with one class →

Ready to Excel in Your Studies?

Get personalised help from Tutopiya's expert tutors. Whether it's IGCSE, IB, A-Levels, or any other curriculum — we match you with the perfect tutor and your first session is free.

Book Your Free Trial