The ISTQB Foundation Study Plan I Would Follow: 4 Weeks, Day by Day
Four weeks, hour by hour: the weekly rhythm that fits a working tester's evenings, the order I would learn the syllabus in, the preparation mistakes that cost people the exam, and how to read a mock result.
Four weeks is the length I would give the ISTQB Foundation exam if I were starting again on a working tester's schedule — not because the syllabus takes four weeks to read, but because it takes four weeks to settle. You can finish reading CTFL v4.0 in two evenings. What you cannot rush is the part where you apply a test design technique correctly with a clock running. So this is a plan about rhythm: what to do on which days, in which order, and how to tell when you are done. For the official numbers — question count, timing and the exact per-chapter split — use our ISTQB CTFL exam structure and official chapter breakdown rather than collecting them from a blog post. And if you are still deciding whether to sit CTFL at all, start with our complete ISTQB Foundation (CTFL v4.0) guide.
The time budget, honestly
The plan assumes 25 to 30 hours in total. That is nothing in the abstract and a great deal on a Tuesday evening after a release, so the budget is deliberately uneven:
Weekdays: one 45–60 minute session, four days out of five. Long enough to cover one topic properly, short enough that you will still do it on a bad day.
Weekend: one block of two to two and a half hours. This is where the work you cannot do tired lives — deriving test cases, question sets, and later full mock exams.
One day off, on purpose. Retention comes from the gaps as much as from the hours.
Five minutes of review to open every session: yesterday's terms, out loud, before anything new.
Two hours a night for six nights buys the same total and a distinctly worse result. Recall improves when the same material is revisited across separated days, and most of the first half of this syllabus is recall.
The order I would learn things in
The obvious move is to follow the chapter numbers; the clever-looking move is to follow the exam weights. I would do neither at the start. Study order should follow dependency: you cannot reason about test levels before you can say precisely what a defect is, and a risk-based testing question is unanswerable while "likelihood" and "impact" are still loose words. Weight decides how many sessions a topic gets — that is what the official chapter breakdown is for — not what comes first.
Vocabulary and principles first. Error, defect, failure. Verification and validation. The seven principles. Everything later is phrased in these words, so an hour here pays interest for three weeks.
The process and lifecycle picture second. Test levels, test types, where testing sits in each development model. It is the frame the later chapters hang on.
Test design techniques third, with a pencil. These are the only tasks in the syllabus you have to perform rather than recognise, and performance needs repetition on separate days.
Test management fourth. The content is not difficult; the questions are long. Reading them accurately is a skill you build by doing question sets, not by reading the chapter twice.
Tools last, and quickly. One session, late enough that it is still fresh on the day.
The four weeks, with the days filled in
Week 1 — get fluent in the language
Two weekday sessions reading the official CTFL v4.0 syllabus, with a notebook open: one line per term, in your own words. Copying a glossary definition does nothing; rewriting it forces you to decide what it means.
Third weekday session: no reading at all. Cover your notes and say the seven principles out loud. Whatever will not come is the agenda for the next session.
Weekend block: your first mock exam, timed, before you feel ready. A low score in week one is not a failure, it is a map — it shows which chapters are already partly there and how the questions are actually worded.
Week 2 — put a pencil in your hand
Static testing takes one session. It is small, stable and mostly about getting the review activities in the right order — a good candidate for a tired evening.
Then one design technique per session, never two in a row: equivalence partitioning on Tuesday, boundary values on Thursday. Each time, use a specification you invented yourself — an age-based discount, a password field, a vending machine — and derive the cases on paper.
Weekend block: forty to fifty questions on what you have covered, then read every rationale, including the ones for options you did not pick. Knowing why a wrong option is wrong is the part that transfers to the next question.
Week 3 — the wordy half
Finish the techniques early in the week: decision tables, state transitions, use cases, statement and branch coverage. Once you can produce the number and not just describe the method, the hardest part of the preparation is behind you.
Then switch to test management, and change how you study with it: read questions, not the chapter. This is where the long scenarios live, and the failure mode here is misreading, not ignorance.
Weekend block: second full timed mock. Compare it with week one chapter by chapter, not as one number.
Week 4 — rehearse, do not learn
One session on tools, and only one. It is the lightest chapter in the exam and it does not deserve a second evening.
Two or three full timed mocks on separate days, each in one sitting, ideally around the hour of day your real exam is booked for.
Between mocks, work only on what the last mock showed you. Week four is not for new material; it is for closing gaps you can name.
The final two days: your own notebook, out loud, and nothing else.
What goes wrong in preparation
Almost none of the preparation mistakes I see are about ability or effort. They are about the shape of the effort.
Reading as if the exam rewarded reading. Highlighting is a comfortable activity that produces the feeling of progress and very little recall. If a session ends and nothing came out of your head, the session did not happen.
Re-taking the same mock. The score rises and the knowledge does not; you are learning that mock. Use a different one each time, and treat any repeat as revision rather than measurement.
Studying the interesting chapters. Test design is satisfying to practise and test management is not, which is exactly why people arrive strong in one and thin in the other.
Cramming the weekend before. It works for material you need tomorrow and it collapses under a clock, because retrieval under pressure is a separate skill from having recently read something.
Learning the techniques by watching. Every derivation you did not write out yourself is a derivation you will not manage at ninety seconds a question.
Never looking at the official sample paper. Style and phrasing are half the difficulty, and they are free to inspect.
How to read a mock result
A single overall percentage is close to useless as feedback. Three things in a result are worth acting on:
The per-chapter split. A comfortable overall score that hides a weak test design chapter is the exact shape of a fail: the light chapters carried the number, and the weak one is where the real exam puts its heaviest weight.
The pattern in the wrong answers. Separate "I did not know this" from "I knew this and misread the question". The first needs study; the second needs a slower first pass on exam day. They are different problems, and the second is the more common one.
Where the time went. If eleven minutes disappeared into the first five questions, your next mock has exactly one goal: flag and move on. Fix the pacing before you spend another evening on content.
And take your scores at their honest value. A mock you have seen before, untimed, at the kitchen table on a Sunday, is not evidence about a proctored exam.
When to stop
Stop taking in new material roughly two days out. Not as superstition: the last forty-eight hours are worth more as consolidation than as intake, and a technique met for the first time on Thursday will not hold on Saturday. Then taper — the day before, one relaxed pass through your own notes, no timed mock, no new chapter. Whether your scores actually mean you are ready is a separate question with a numeric answer, and it lives on the how to pass guide.
Where the practice comes from
A plan like this is only as good as the questions you feed it. Full length, timed, a rationale on every option, and a result broken down by chapter — those four properties are what make a mock useful rather than merely reassuring. Ours are here: ExamCaliber's CTFL Foundation mock exams. Pick a different one each week, and let the chapter breakdown of the result choose what you study next.
Frequently asked
Experienced testers sometimes do it, but a week only leaves room for reading, and reading is the part that does not decide the result. The test design techniques need repetition across separate days, and you need at least two full timed mocks. If a week is all you have, spend three of the seven days on techniques and mocks rather than on a second pass through the syllabus.
Then stretch the plan to six weeks instead of compressing the sessions. Thirty focused minutes on five days is worth more than a single Saturday marathon, but it is not enough to both learn a technique and practise it in one sitting, so give each technique two short sessions on different days.
Follow dependency, not chapter numbers and not exam weight: vocabulary and principles first, then the lifecycle and process picture, then the test design techniques with a pencil, then test management, and tools last. Weight decides how much time each topic gets, not what comes first.
Plan for four or five in total: one early and deliberately unprepared, one at the halfway point, and two or three in the final week on separate days. Take a different mock each time — re-taking one you have already seen measures your memory of that mock, not your readiness.
Stop taking in new material about 48 hours before the exam. The last two days are worth more as consolidation than as intake, and a technique you meet for the first time on Thursday will not hold up on Saturday. The day before: one relaxed pass through your own notes, no timed mock.
Self-study is enough for most working testers, because the syllabus is public and the exam is closed book. A course mainly buys you structure and a deadline. If you know you will not keep to a schedule on your own, that is a real reason to pay for one; if you will, the money is better spent on practice questions.
Part of the ExamCaliber editorial team. Every ExamCaliber question and rationale is written and reviewed by hand against the current syllabus — never scraped from exam dumps.