ISTQB® CTFL 4.0 is the current version of the Certified Tester Foundation Level, the entry-level certification in the ISTQB® scheme. It tests whether you understand the core ideas of software testing: why we test, how testing fits into development, how to design tests, and how test work is managed. The exam has 40 multiple-choice questions, you get 60 minutes (75 if the exam isn't in your first language), and you need 26 correct answers (65%) to pass. There are no formal prerequisites, so anyone can sit it.
The rest of this post covers what each part of the exam asks about, what is different in version 4.0, and how to prepare without wasting effort.
What CTFL 4.0 actually is
CTFL stands for Certified Tester Foundation Level. The "4.0" refers to the version of the syllabus the exam is based on. Version 4.0 replaced the earlier v3.1 syllabus, so if you are studying today, 4.0 is the one that matters.
The Foundation Level is the base of the ISTQB® certification path. Advanced and specialist certifications build on it, which is why many testers treat it as their first step. It is also taken by people who aren't full-time testers: developers, business analysts, product owners and career changers who want a shared vocabulary for quality and testing.
The exam format at a glance
- 40 multiple-choice questions, each worth one point
- 60 minutes, or 75 minutes if you take the exam in a language that isn't your first
- 26 correct answers (65%) needed to pass
- Most questions have one correct answer from four options; some ask you to choose two
- Wrong answers don't cost you points, so never leave a question blank
That works out to roughly a minute and a half per question. Most questions take less; the ones that ask you to apply a test technique take more.
The six chapters and how many questions each one gets
The syllabus is split into six chapters, and the exam draws a fixed number of questions from each: 8, 6, 4, 11, 9 and 2. Knowing this split is the single most useful thing for planning your study time.
1. Fundamentals of Testing (8 questions)
The big picture: what testing is for, how it differs from debugging, the seven testing principles, the main test activities from planning through to completion, the work products testing produces, and traceability between them. It also covers the skills testers need, the whole-team approach, and the pros and cons of independent testing.
2. Testing Throughout the Software Development Lifecycle (6 questions)
How the way a team builds software shapes the way it tests. Expect test-first approaches (TDD, ATDD, BDD), DevOps, shift left, and retrospectives, alongside the classic material on test levels, test types, confirmation and regression testing, and maintenance testing.
3. Static Testing (4 questions)
Finding problems without running the code, mainly through reviews. You need to know why early feedback is valuable, the steps of a review, the roles people play in one, and how the different review types compare, from informal reviews up to inspections.
4. Test Analysis and Design (11 questions)
The largest chapter and the most hands-on. It covers:
- Black-box techniques: equivalence partitioning, boundary value analysis, decision table testing and state transition testing
- White-box techniques: statement testing and branch testing
- Experience-based techniques: error guessing, exploratory testing and checklist-based testing
- Collaboration-based approaches: writing user stories together, acceptance criteria, and acceptance test-driven development
Many questions here give you a small scenario and ask you to work something out, such as how many test cases a technique needs or which values sit on a boundary.
5. Managing the Test Activities (9 questions)
The planning and control side of testing: test plans, entry and exit criteria, estimation techniques, test case prioritization, the test pyramid, the testing quadrants, risk-based testing, monitoring and reporting, configuration management, and defect reports. Some of these, like estimation and prioritization, also show up as small calculation or ordering questions.
6. Test Tools (2 questions)
A short chapter on what kinds of tools support testing and the benefits and risks of test automation. Two questions is not many, but they are usually quick points if you have read the material.
What changed from v3.1 to v4.0
If you are using older notes or books, be aware of the main shifts:
- More agile and DevOps thinking throughout. The whole-team approach, shift left, test-first development and retrospectives are now part of the core syllabus rather than a separate add-on.
- Collaboration-based test approaches were added to the test design chapter.
- The test pyramid and testing quadrants now sit in the Foundation Level syllabus.
- White-box coverage focuses on statement and branch testing, and the black-box list was trimmed.
- Terminology and structure were reworked, so chapter numbering and some wording in v3.1 materials won't line up.
The practical takeaway: study from material written for 4.0. Older practice questions can test techniques or terms that are no longer examined, and can miss topics that now are.
Understanding K-levels
Every learning objective in the syllabus is tagged with a knowledge level:
- K1 (Remember): recognize a term or fact
- K2 (Understand): explain, compare or classify ideas
- K3 (Apply): use a technique on a concrete example
Most of the exam sits at K2, so memorizing definitions isn't enough; you need to understand why things are the way they are. The K3 questions cluster in chapter 4, with a few in chapter 5. These are the ones where practice pays off most.
A practical way to prepare
- Read the syllabus once, start to finish. Don't try to memorize it on the first pass. Just get the map of what's covered.
- Weight your time by question count. Chapters 4 and 5 together are 20 of the 40 questions. Chapter 6 is two. Spend your hours accordingly.
- Work the test techniques by hand. Draw the partitions, list the boundary values, fill in decision tables, trace state diagrams, count branches. Doing a dozen examples beats rereading the theory.
- Learn the vocabulary precisely. The exam often hinges on the difference between similar terms: error, defect and failure; verification and validation; test level and test type. Our CTFL glossary is a good place to check yourself.
- Take full, timed practice exams. This builds pacing and shows which chapters are costing you points. After each one, review every question you missed, and also why each wrong option was wrong.
- Read every question twice. Watch for words like NOT, MOST and BEST, and for questions that ask you to select two answers.
Many people are ready after a few weeks of steady study, but it depends on your background. Someone who already works in testing will move faster through chapters 1 and 2; a career changer may need more time on the techniques in chapter 4.
Booking the exam
You can take CTFL 4.0 through an exam provider such as Pearson VUE, Kryterion or iSQI, depending on where you are and how you want to sit it. The booking steps, costs and options differ between providers, so check the details before you pick a date. Our exam booking guide walks through the process.
Next step
If you want to see where you stand right now, try the free simul8R practice exam. It runs on the same kind of screen as the real exam provider, so you get used to the interface as well as the questions. And if you'd prefer guided preparation, our live CTFL 4.0 course covers every chapter with an ISTQB®-certified instructor.