The ISTQB Certified Tester Foundation Level (CTFL) 2023 syllabus is the definitive guide to what's on your exam. If you're preparing for ISTQB Foundation Level, this document is your curriculum — not any textbook, not any course, not this article.
That said, 75 pages of dense certification text isn't easy to navigate on your own. This guide breaks it down chapter by chapter: what's covered, what's important, and what changed from the previous 2018 version.
What Is the ISTQB CTFL Syllabus?
The syllabus is published by the International Software Testing Qualifications Board (ISTQB) and defines the learning objectives for the Foundation Level certification. Every accredited training provider and every exam question must align to it.
The 2023 version replaced the 2018 version and introduced notable structural changes — most significantly, an increased focus on Agile testing and a streamlined treatment of test techniques.
You can download the official syllabus for free at istqb.org.
The Six Chapters at a Glance
| Chapter | Title | Weight (approx.) |
|---|---|---|
| 1 | Fundamentals of Testing | ~26% |
| 2 | Testing Throughout the SDLC | ~17% |
| 3 | Static Testing | ~11% |
| 4 | Test Analysis and Design | ~25% |
| 5 | Managing the Test Activities | ~17% |
| 6 | Test Tools | ~4% |
Chapters 1 and 4 together account for about half the exam. Don't neglect the others — but these two deserve the most study time.
Chapter 1: Fundamentals of Testing
This chapter establishes the conceptual foundation. It covers:
- Why testing is necessary — the cost of software failures, the value of early defect detection
- Testing and quality assurance — the difference between QA (process-focused) and testing (product-focused)
- Testing principles — there are seven, and you need to know all of them by name and be able to recognize examples of each
- The test process — the six activities: planning, monitoring & control, analysis, design, implementation, execution, and completion
- The psychology of testing — cognitive biases, independence of testing, communication between testers and developers
- Testware — what artifacts testing produces (test plans, test cases, defect reports, etc.)
The 7 Testing Principles are a perennial exam topic. Learn them in order if it helps, but more importantly, understand what each one means in practice:
- Testing shows the presence of defects, not their absence
- Exhaustive testing is impossible
- Early testing saves time and money
- Defects cluster together
- The pesticide paradox
- Testing is context dependent
- Absence-of-errors is a fallacy
Chapter 2: Testing Throughout the SDLC
This chapter links testing to software development models. The core message: testing activities should be integrated throughout the development lifecycle, not bolted on at the end.
Key topics:
- Software development models — how sequential (waterfall), iterative, and incremental models each affect when and how testing happens
- Test levels — unit testing, integration testing, system testing, and acceptance testing. Know which types of defects each level is best at catching.
- Test types — functional testing, non-functional testing (performance, usability, security, etc.), structural testing, and change-related testing (regression, confirmation)
- Maintenance testing — testing existing systems after changes; triggers and scope
What changed in 2023: The 2018 version had separate sections for Agile testing. In 2023, Agile considerations are woven throughout the chapter rather than isolated, reflecting how common Agile is in practice.
Chapter 3: Static Testing
Static testing means reviewing artifacts without executing code. It's less glamorous than dynamic testing, but it's a powerful defect-prevention tool — and it shows up on the exam.
Key topics:
- Static testing vs. dynamic testing — both test work products, but through different means
- The review process — from informal reviews to rigorous inspections, with defined roles and steps
- Review types:
- Informal review — no defined process; flexible
- Walkthrough — author-led; goals include learning and defect detection
- Technical review — peer-driven; focuses on correctness
- Inspection — the most formal; entry/exit criteria, metrics, follow-up
- Roles in formal reviews: moderator, author, reviewer, scribe, manager
- Static analysis — tool-based analysis of code without execution; finds coding standard violations, security vulnerabilities, dead code
A common exam question type: given a scenario, identify which type of review is being described.
Chapter 4: Test Analysis and Design
This is the most practical chapter — and the source of most K3 (apply-level) questions. You need to be able to use these techniques, not just describe them.
Black-box techniques (based on specification, not code):
Equivalence Partitioning (EP): Divide input data into partitions where all values in a partition are expected to behave the same. Test one value from each partition.
Boundary Value Analysis (BVA): Focus on the values at the edges of partitions. 2-value BVA tests the boundary and its neighbor; 3-value BVA adds the other side.
Decision Table Testing: Model combinations of conditions and actions in a table. Useful for business rules with multiple inputs.
State Transition Testing: Model behavior based on states, transitions, events, and guards. Useful for systems with distinct operational states.
Use Case Testing: Derive tests from use cases — scenarios, alternative flows, exceptional flows.
White-box techniques (based on code structure):
Statement Coverage: Every executable statement is executed at least once.
Branch/Decision Coverage: Every possible branch (true/false) from every decision point is taken. This subsumes statement coverage.
Experience-based techniques:
Error guessing: Use experience and intuition to identify likely defects.
Exploratory testing: Simultaneous learning, test design, and execution.
Checklist-based testing: Use a prepared list of conditions to check.
Chapter 5: Managing the Test Activities
This chapter covers the management and organizational side of testing.
Key topics:
- Test planning — objectives, scope, approach, resources, schedule. Know the purpose and typical content of a test plan.
- Risk-based testing — product risk (things that could go wrong with the software) vs. project risk (things that could go wrong with the project). Risk is used to prioritize testing.
- Test monitoring and control — metrics used to track progress (defect density, test execution rate, etc.); what triggers control actions
- Configuration management — how testware and test items are versioned and controlled
- Defect management — the defect lifecycle from discovery through closure; what makes a good defect report
The distinction between product risk and project risk is a reliable exam question topic.
Chapter 6: Test Tools
The shortest chapter — about 4% of exam weight. But don't skip it entirely.
Key topics:
- Categories of test tools — management tools, static analysis tools, test design tools, execution tools, performance tools, etc.
- Benefits and risks of tool introduction — don't assume new tools always improve things
- Tool selection criteria — what to evaluate when choosing a tool for your context
- Pilot projects — why you should run one before full adoption
One key message from this chapter: tools support the testing process, but they don't replace tester judgment.
What Changed from CTFL 2018 to CTFL 2023?
The 2023 syllabus was a significant update, not just a revision. Key changes:
- Agile testing is no longer a separate extension — Agile context is woven into the main syllabus throughout
- Test techniques were streamlined — some 2018 techniques (like cause-effect graphing as a standalone topic) were consolidated
- The test process model was updated — cleaner activity definitions
- Increased emphasis on shift-left — testing earlier in the lifecycle is more explicitly encouraged
- Glossary alignment — term definitions were updated to align with the ISTQB Glossary 4.0
If you're using study materials from before 2024, check whether they're based on the 2018 or 2023 syllabus. Some content will overlap, but the exam questions are written against the 2023 version.
Where to Practice
The best way to test your syllabus knowledge is with real ISTQB exam questions. istqbexam.com has all 423 questions from official ISTQB sample exams — free, no sign-up.
Use the exam set view to practice chapter by chapter, or jump into a full 40-question timed simulation to see where you stand.