Passing the ISTQB Foundation Level exam is less about years of experience and more about knowing the syllabus the way the exam writers do. This guide shows you exactly what to study, in what order, and how to answer the tricky questions, with day-by-day plans you can follow.
ISTQB CTFL › Preparation guide and study plan Syllabus v4.0.1 · updated 3 Nov 2026
How the exam is written
Every exam question is mapped to one learning objective (LO) in the syllabus, and ISTQB fixes how many questions come from each chapter and at which knowledge level. That makes the exam predictable:
- The syllabus is the only source. If your company, a blog or a video uses a term differently, the exam follows the syllabus and the ISTQB Glossary.
- Keywords are K1-examinable. Every keyword listed at the start of a chapter can appear in a “which statement is true” question.
- K3 questions are calculations or scenarios. There are exactly 8, all from chapters 4 and 5.
- Wrong options are usually true statements about a different concept. You must know which concept a statement belongs to, not just whether it sounds right.
| Chapter | Questions | Hours to plan | Priority |
|---|---|---|---|
| 1. Fundamentals of Testing | 8 | 5 | High |
| 2. Testing Throughout the SDLC | 6 | 3 | Medium |
| 3. Static Testing | 4 | 2 | Medium |
| 4. Test Analysis and Design | 11 | 8 | Highest |
| 5. Managing the Test Activities | 9 | 6 | Highest |
| 6. Test Tools | 2 | 1 | Low |
| Sample papers and revision | 40 | 7 | Highest |
Your study toolkit
- The official CTFL v4.0.1 syllabus (free PDF on istqb.org). Read it at least twice. It is about 60 pages of examinable text.
- Our chapter notes (links in the course menu), which explain each section in plain language with examples.
- The ISTQB Glossary for exact definitions. Look up every keyword you are not sure about.
- Our three sample papers plus official sample exams A to D. Do them timed, then study every explanation, including for the questions you got right.
- A one-page “formula sheet” you make yourself: EP and BVA rules, decision-table coverage, state-transition coverage, three-point estimation, the seven principles, review roles and review types.
4-week study plan (1 to 1.5 hours a day)
| Day | Task |
|---|---|
| 1 | Read the certification guide. Download the syllabus and glossary. Skim the syllabus once, end to end, without trying to memorise. |
| 2-3 | Chapter 1: test objectives, testing vs debugging, testing vs QA, error/defect/failure/root cause. |
| 4 | Chapter 1: the seven principles. Write one real-life example of each. |
| 5 | Chapter 1: test activities, testware, traceability, roles, skills, whole-team approach, independence. Do the chapter self-check. |
| 6-7 | Chapter 2: SDLC impact, good practices, TDD/ATDD/BDD, DevOps, shift left, retrospectives. |
| 8 | Chapter 2: test levels, test types, confirmation vs regression, maintenance testing. Self-check. |
| 9 | Chapter 3: static testing, review process, roles, review types, success factors. Self-check. |
| 10 | Revision day: chapters 1-3. Re-read the syllabus for those chapters. |
| 11-12 | Chapter 4: equivalence partitioning and boundary value analysis. Solve at least 10 problems. |
| 13 | Chapter 4: decision tables. Build three tables from small business rules. |
| 14 | Chapter 4: state transition testing. Draw two state diagrams and count all three coverage types. |
| 15 | Chapter 4: statement and branch testing, value of white-box testing. |
| 16 | Chapter 4: error guessing, exploratory and checklist-based testing; user stories, acceptance criteria, ATDD. Self-check. |
| 17-18 | Chapter 5: test plan, tester in planning, entry/exit criteria, estimation (practise all four techniques), prioritization, test pyramid, testing quadrants. |
| 19 | Chapter 5: risk (likelihood, impact, project vs product risk, mitigation). |
| 20 | Chapter 5: metrics, reports, configuration management, defect report. Self-check. |
| 21 | Chapter 6 and a full read of the syllabus keywords lists. Update your formula sheet. |
| 22 | Sample paper 1, timed (60 minutes). Review every answer. |
| 23 | Re-study the LOs you got wrong. |
| 24 | Sample paper 2, timed. Review. |
| 25 | Official sample exam A, timed. Review the official answer explanations. |
| 26 | Sample paper 3 and official sample exam B, timed. Review. |
| 27 | Weak areas only, plus your formula sheet. Official sample exam C or D if time allows. |
| 28 | Light revision, read the keyword lists, sleep early. Exam day is next. |
2-week fast-track plan (3 to 4 hours a day)
| Day | Task |
|---|---|
| 1 | Chapter 1 complete + self-check |
| 2 | Chapter 2 complete + self-check |
| 3 | Chapter 3 complete + revision of chapters 1-3 |
| 4 | Chapter 4: EP, BVA, decision tables (with 15 practice problems) |
| 5 | Chapter 4: state transitions, white-box, experience-based, collaboration-based |
| 6 | Chapter 5: planning, estimation, prioritization, pyramid, quadrants |
| 7 | Chapter 5: risk, monitoring, reporting, configuration and defect management; chapter 6 |
| 8 | Sample paper 1 (timed) and full review |
| 9 | Fix weak LOs; re-read the matching syllabus sections |
| 10 | Sample paper 2 + official sample exam A |
| 11 | Fix weak LOs |
| 12 | Sample paper 3 + official sample exam B |
| 13 | Official sample exam C or D; formula sheet; keyword lists |
| 14 | Light revision only |
Book the exam when you score 32 or more out of 40 (80%) on two different full papers you have not seen before. The real pass mark is 26, so this gives you a safety margin for nerves and unfamiliar wording.
The 8 K3 skills you must practise
These are the only “apply” learning objectives. Each is worth practising until you can do it in under 3 minutes.
1. Equivalence partitioning (FL-4.2.1)
A form accepts an age from 18 to 60 (whole numbers). Partitions: below 18 (invalid), 18 to 60 (valid), above 60 (invalid). One value from each partition gives 100% EP coverage with 3 test cases, for example 10, 35 and 75. Invalid partitions count as coverage items too.
2. Boundary value analysis (FL-4.2.2)
Same field. The boundary values are the minimum and maximum of every partition: 17, 18, 60 and 61.
- 2-value BVA: each boundary value plus its closest neighbour in the adjacent partition. The set is {17, 18, 60, 61}, so 4 test values.
- 3-value BVA: each boundary value plus both neighbours. For 17: 16, 17, 18. For 18: 17, 18, 19. For 60: 59, 60, 61. For 61: 60, 61, 62. Removing duplicates gives {16, 17, 18, 19, 59, 60, 61, 62}, so 8 test values.
ISTQB counts the boundaries of the invalid partitions too, and removes duplicate values. If a question asks for coverage, divide the values exercised by the total identified, exactly as the syllabus defines it.
3. Decision table testing (FL-4.2.3)
A shop gives free delivery if the customer is a member or the order is over ₹999, and an extra 5% discount only if the customer is a member and pays online. With three Boolean conditions there are 2 × 2 × 2 = 8 columns in the full table. Coverage items are the feasible columns, so 100% coverage needs 8 test cases (fewer only if columns are merged or infeasible).
4. State transition testing (FL-4.2.4)
A login screen has states Ready, Locked and Logged in. Learn the three coverage criteria:
- All states coverage: every state visited at least once.
- Valid transitions (0-switch) coverage: every valid transition exercised. Most common criterion.
- All transitions coverage: every valid transition exercised and every invalid transition attempted, one invalid transition per test case.
Full valid-transitions coverage guarantees full all-states coverage, and all-transitions coverage guarantees both.
5. ATDD (FL-4.5.3)
Given a user story and its acceptance criteria, pick the test case that checks a criterion, with positive cases first, then negative and non-functional ones. Each test must be understandable by business stakeholders.
6. Estimation (FL-5.1.4)
Three-point estimation: E = (a + 4m + b) / 6 and SD = (b − a) / 6. Example: optimistic a = 4, most likely m = 6, pessimistic b = 14 person-days gives E = (4 + 24 + 14) / 6 = 7, SD = 10 / 6 ≈ 1.67, so 7 ± 1.67 person-days.
Ratio estimation: if a past project had a development-to-test ratio of 5:2 and the new development effort is 500 person-days, the test effort is 500 × 2 / 5 = 200 person-days.
7. Test case prioritization (FL-5.1.5)
Order by risk, coverage (or additional coverage) or requirement priority, but a test that another test depends on must run first, even if its own priority is lower. Exam questions almost always hide one dependency.
8. Defect report (FL-5.5.1)
Know what a good report contains: unique ID, title and short summary, date, author, test object and environment, context (test case, test activity, SDLC phase), description with steps to reproduce, expected and actual results, severity, priority, status, and references such as the test case. Questions ask which information is missing or which report is best.
How to read a question
- Read the last line first. It tells you what is asked: “BEST”, “MOST likely”, “NOT”, “FIRST”.
- Underline the qualifier. “Which is NOT a benefit of…” flips the logic. One missed “NOT” costs a mark.
- Name the concept. Before reading the options, say which LO the question tests. Then each option is either about that concept or a distractor about a neighbouring one.
- Eliminate absolutes. Options with “always”, “never”, “guarantees” or “proves” are usually wrong (“testing proves there are no defects” breaks principle 1).
- Choose the syllabus answer, not your company’s answer. If two options are both true in real life, pick the one the syllabus states.
- Show your working on K3 questions. Use the scratch paper or on-screen notes and write the partitions, boundaries or table columns before choosing.
Time management
You have 60 minutes for 40 questions. Aim for about 1 minute on K1 and K2 questions and 3 minutes on K3 questions. Answer every question on the first pass, flag the ones you are unsure about, and use the last 10 minutes to review flags. Never leave a question blank.
Common traps
| Trap | What the syllabus says |
|---|---|
| “Testing and debugging are the same” | Testing finds failures or defects; debugging finds, analyses and removes their causes. |
| “QA and testing are the same” | Testing is product-oriented and corrective (quality control); QA is process-oriented and preventive. |
| “Static testing causes failures” | Static testing finds defects directly; it cannot cause failures because nothing is executed. |
| “Confirmation testing = regression testing” | Confirmation checks a fix; regression checks that changes did not break anything else. |
| “100% statement coverage means 100% branch coverage” | It is the other way round: branch coverage subsumes statement coverage. |
| “All states coverage is the strongest” | It is the weakest of the three state-transition criteria. |
| “Independent testers are always better” | Independence has drawbacks: isolation, lost developer responsibility, bottlenecks. |
| “Exit criteria are only about test coverage” | They also include other measures of thoroughness (unresolved defects, defect density, failed tests) and yes/no criteria. Running out of time or budget can be a valid exit criterion if stakeholders accept the risk. |
| “Planning Poker is a separate technique” | It is a variant of Wideband Delphi. |
Exam-day checklist
- A valid government photo ID that matches your registration name exactly.
- For online exams: the Pearson VUE system test passed on the same computer and network, a quiet room, a clear desk, webcam and microphone working, other apps closed.
- For test centres: arrive 30 minutes early.
- Eat, hydrate and keep 5 minutes of slack in your schedule before check-in.
- During the exam: answer everything, flag doubts, review flags at the end.
Practise the method
A field accepts whole numbers from 1 to 100. Using 2-value boundary value analysis, how many test values are needed for 100% coverage?
- A. 2
- B. 4
- C. 6
- D. 8
Show answer
Answer: B. 4
Partitions are ≤0, 1 to 100, and ≥101. The boundary values are 0, 1, 100 and 101. In 2-value BVA each boundary value and its closest neighbour in the adjacent partition are covered, and these four values already include all the neighbours.
Three-point estimates for a test task are a = 2, m = 5 and b = 14 days. What is the estimate E?
- A. 5 days
- B. 6 days
- C. 7 days
- D. 8 days
Show answer
Answer: B. 6 days
E = (2 + 4 × 5 + 14) / 6 = 36 / 6 = 6 days. The standard deviation is (14 − 2) / 6 = 2 days.
Test T1 (priority 1) can only run after test T3 (priority 3) has created the test data. Which test runs first?
- A. T1, because it has the highest priority
- B. T3, because T1 depends on it
- C. Either, because priority decides the order
- D. Neither, until the dependency is removed
Show answer
Answer: B. T3, because T1 depends on it
The syllabus says that if a higher-priority test depends on a lower-priority one, the lower-priority test must be executed first.