How to Prepare for the ISTQB CTFL Exam
The Foundation Level exam is passed by preparation that matches its shape. Half the questions come from two chapters, a fifth of them need you to work something out, and the rest reward precise reading of a syllabus you can download for free. The plan below is built around those three facts.
How long does it take to prepare?
Plan on two to six weeks, depending on how much testing you already know. A useful anchor is the syllabus itself. An accredited course must teach it for at least 1135 minutes, about 19 hours, and a classroom course usually fits that into three or four days. Self-study takes longer than a course, because nobody is filtering what matters, and you also need time for practice questions. Our estimate for self-study is somewhere between 25 and 40 hours in total.
An hour or so on weekdays with a longer session at the weekend fits the four-week plan below. If you already work in testing and know the vocabulary, two weeks of the same plan compressed is realistic. If software testing is new to you, give it six weeks and spend the extra time in weeks 2 and 3.
A four-week plan
The plan follows the syllabus order, because each chapter leans on the vocabulary of the ones before it. It front-loads the cheap marks, puts the heaviest chapter in a week of its own, and leaves the last week for fixing what the mock exams show you.
Week 1: Chapters 1 to 3, and a baseline
18 of the 40 questions, all recall and understanding.
- Before reading anything, sit one full mock exam cold. The score is not a verdict. It tells you where you start and which chapters are already familiar.
- Read chapters 1, 2 and 3 of the syllabus. They are short, and the ideas in them are reused by every later chapter.
- Look up each chapter keyword in the glossary as you meet it, and make a flashcard for any you cannot define from memory.
- Finish the week with one drill per chapter.
Take the baseline mock examChapter 1 drillChapter 2 drillChapter 3 drill
Week 2: Chapter 4, with a pencil
11 questions, and five of the eight K3 objectives.
- Read chapter 4 once for the ideas, then again with paper, working every example yourself.
- Practise one technique per session: equivalence partitioning, boundary value analysis, decision tables, state transitions. Do not move on until you can count test cases without checking the answer.
- Write test cases from a user story's acceptance criteria, the way ATDD does. This is the fifth K3 objective and the easiest one to forget.
- Learn statement versus branch coverage and the experience-based techniques. These are K2, so understanding beats arithmetic here.
Boundary value analysis worked examplesK3 chapter 4 drillChapter 4 drill
Week 3: Chapters 5 and 6
11 questions, three K3 objectives among them.
- Read chapter 5. It is long and its vocabulary overlaps, so separate test planning, monitoring, control and completion clearly in your notes.
- Work through estimation, building a test execution schedule from priorities and dependencies, and the contents of a defect report. Each is a K3 objective.
- Read chapter 6 in one sitting. It supplies two questions.
- Sit a second full mock exam at the end of the week and compare it chapter by chapter with your baseline.
Chapter 5 drillChapter 6 drillWorked questions by chapter
Week 4: Close the gaps
Turn a borderline score into a safe one.
- List every chapter and K-level where you are dropping marks, and spend each day on the worst one.
- Sit a full timed mock exam every second day. Review every answer you got wrong and every one you guessed right.
- Read the syllabus through one last time. Things that confused you in week 1 will now make sense, and a few details you skipped will turn out to matter.
- Book the exam once you pass the mock several times running with marks to spare. If you are not there, add a week rather than hoping.
Practice test 1Practice test 2Practice test 3Drills by K-level
Using mock exams properly
Mock exams are the most useful preparation tool and the most misused. Retaking the same paper until the score climbs measures your memory of that paper, not your grasp of the syllabus. Two habits avoid that. Use a mock that draws a fresh set of questions each time, and spend longer reviewing an attempt than you spent sitting it.
In the review, sort each miss into one of three piles. A term you could not define is a glossary gap, and flashcards fix it. A concept you confused with a neighbouring one is an understanding gap, and rereading that syllabus section fixes it. A calculation you got wrong or ran out of time on is a practice gap, and only more questions of that kind fix it. The K-level of the question usually tells you which pile it belongs in.
One warning about “dumps”. Sites selling what they claim are real exam questions are breaking the exam rules, and the questions are often wrong. Candidates who memorise answers without the reasoning are the ones who fail when the real paper words a familiar idea differently.
On exam day
- Go through the paper once answering everything you are sure of, flagging the rest. Calculation questions go in the second pass.
- Watch for NOT, MOST and BEST in the stem. Underline them mentally before you look at the options.
- Answer with the syllabus in mind, not your workplace. Where your team does things differently, the exam wants the ISTQB answer.
- Never leave a blank. A wrong answer loses nothing, so an educated guess between two remaining options is free.
- If the exam is not in your first language, make sure you asked for the extra 15 minutes when booking.