FREE ISTQB Foundation Level (CTFL) Exam Guide 2026: Pass on First Try (Syllabus v4.0, 65%, 40 Questions, Free Sample Exams)

ISTQB Foundation Level (CTFL) Exam Guide 2026: The Complete Syllabus v4.0 Walkthrough

The ISTQB Certified Tester Foundation Level (CTFL) is the world's most widely recognized software testing credential — with more than 1.2 million certifications issued across 130+ countries since ISTQB launched in 2002. In 2026 the exam is based on the CTFL Syllabus v4.0, released in April 2023 and still the current standard. If you are aiming for a QA Engineer, Test Analyst, or SDET role, CTFL is the baseline your hiring manager expects to see.

This 2026 guide walks you through every chapter of CTFL Syllabus v4.0, works through the exact test-design techniques you will be tested on (equivalence partitioning, boundary value analysis, decision tables, state transition, use case testing), maps the K-level cognitive demands on each Learning Objective, shows you the real cost path via ASTQB (American Software Testing Qualifications Board), and gives you a 4-6 week study plan built around the free official resources.

You do not need a $1,500 bootcamp to pass CTFL. The ISTQB Syllabus v4.0 PDF is free, the four official ISTQB Sample Exams (A, B, C, D) are free, and our CTFL practice bank is free.

ISTQB CTFL Exam At-a-Glance (2026)

Source: ISTQB CTFL Syllabus v4.0 (istqb.org), ASTQB 2026 pricing page. Confirm current fees directly on astqb.org before registering.

---

Start Your FREE CTFL Prep Today

Start FREE ISTQB CTFL Practice QuestionsPractice questions with detailed explanations

Practice every chapter of Syllabus v4.0 — Fundamentals of Testing, Testing Throughout the SDLC, Static Testing, Test Analysis & Design, Managing Test Activities, and Test Tools — with AI-powered explanations mapped to each Learning Objective and K-level. 100% FREE.

---

Who Should Take the ISTQB CTFL Exam?

CTFL is designed for anyone involved in software testing, regardless of development methodology or industry. Its target audience is broader than most testing certifications:

• Manual QA testers transitioning from ad-hoc testing to a structured testing discipline
• Junior QA engineers and career-changers who need a globally recognized baseline credential
• Software developers adding test-design fluency to move toward SDET/automation roles
• Business analysts who write acceptance criteria and need shared vocabulary with test teams
• Scrum Masters and Product Owners on teams that rely on quality engineering
• Test managers who need the foundation before advancing to CTAL-TM
• Anyone preparing for Specialist Levels (Agile Tester, Mobile, Automotive, Security, AI) — CTFL is the mandatory prerequisite for most

There are no eligibility prerequisites. You do not need a degree, work experience, or instructor-led training. Just self-study, an ID, and the exam fee.

CTFL Syllabus v4.0: The Six Chapters and Their Weightings

CTFL Syllabus v4.0 publishes an explicit blueprint in Table 0-2 showing the minutes allocated to each chapter in an accredited training course, which approximates the weighting of exam items. Use these as your study-time targets.

Source: ISTQB CTFL Syllabus v4.0, Table 0-2 (Time Allocation by Chapter). Always confirm the current edition on istqb.org/certifications/certified-tester-foundation-level.

Key insight: Chapters 4 (Test Analysis & Design) and 5 (Managing Test Activities) together account for roughly 50% of the exam. Most candidates who fail under-study these two chapters. Budget at least half of your study time accordingly.

---

Chapter 1 — Fundamentals of Testing (~16%)

This chapter introduces the vocabulary you will use for the rest of your career. Expect K1/K2 items on definitions, the seven testing principles, and the test process.

High-yield concepts:

• Testing vs debugging — testing finds defects; debugging removes them.
• Objectives of testing — prevent defects, find failures, evaluate work products, reduce risk, comply with requirements/contracts.
• The seven testing principles (memorize the order):
  1. Testing shows the presence, not the absence, of defects
  2. Exhaustive testing is impossible
  3. Early testing saves time and money
  4. Defects cluster together (the Pareto principle — ~80% of defects in ~20% of modules)
  5. Tests wear out (the pesticide paradox)
  6. Testing is context dependent
  7. Absence-of-defects is a fallacy
• Test process activities — test planning, monitoring & control, analysis, design, implementation, execution, completion
• Error vs defect vs failure — an error (mistake by a person) leads to a defect (flaw in the code), which may cause a failure (observable wrong behavior)
• The testing mindset — curiosity, attention to detail, experience, skepticism, communication

Exam trap: a question that lists "prove the software is defect-free" as an objective of testing — this is always wrong because of principle 1 and principle 7.

---

Chapter 2 — Testing Throughout the SDLC (~16%)

Tests your understanding of how testing fits into the software lifecycle, including both sequential and Agile models.

High-yield concepts:

• Test levels — Component (unit), Integration (component integration, system integration), System, Acceptance
• Test types — Functional, Non-functional, Black-box, White-box, Change-related (confirmation + regression)
• The test pyramid — Mike Cohn's model: many unit tests at the base, fewer integration tests in the middle, very few UI/E2E tests at the top. The point: lower-level tests are cheaper and faster.
• Agile Testing Quadrants — Lisa Crispin and Janet Gregory's model:
  • Q1 (Technology-facing, support team) — Unit tests, component tests
  • Q2 (Business-facing, support team) — Functional tests, examples, story tests, prototypes
  • Q3 (Business-facing, critique product) — Exploratory testing, scenarios, usability
  • Q4 (Technology-facing, critique product) — Performance, security, "-ilities"
• Shift-left — moving testing earlier (reviews, static analysis, TDD, BDD)
• Maintenance testing — re-testing when the software is modified, migrated, or retired

Exam trap: confusing test levels (component/integration/system/acceptance) with test types (functional/non-functional/white-box/change-related). The Syllabus v4.0 is explicit that these are orthogonal dimensions.

---

Chapter 3 — Static Testing (~10%)

Static testing is testing without executing the code — reviews and static analysis.

High-yield concepts:

• Benefits of static testing — defects found earlier are cheaper; some defects can only be found statically (e.g., dead code, unreachable code, violations of standards)
• Work products that can be reviewed — requirements, user stories, design, code, test cases, user documentation
• Four review types in Syllabus v4.0 (memorize all four, from least to most formal):

• Review roles — Author, Manager, Facilitator/Moderator, Review Leader, Reviewer, Scribe
• Review process activities — Planning, Initiating review, Individual review, Issue communication and analysis, Fixing and reporting
• Success factors — appropriate review type for the work product, trained participants, no blame culture, management support

Exam trap: "Walkthroughs are the most formal review type" — wrong. Inspections are the most formal.

---

Chapter 4 — Test Analysis and Design (~26%)

This is the largest chapter on the exam and the source of most K3 (application-level) questions. You must be able to apply techniques, not just recognize them.

Test Design Techniques — The Big Three Categories

Worked Example 1: Equivalence Partitioning + Boundary Value Analysis

Suppose a field accepts an integer age from 18 to 65 inclusive. Determine the test cases.

Equivalence Partitioning (EP) — divide the input domain into partitions where the system should behave the same way:

• Invalid partition 1: age < 18 (e.g., 10)
• Valid partition: 18 <= age <= 65 (e.g., 40)
• Invalid partition 2: age > 65 (e.g., 80)

EP gives you 3 test values (one from each partition).

Boundary Value Analysis (BVA) — test values at and around each boundary (2-value BVA tests the boundary and one side; 3-value BVA tests the boundary and both sides):

• 2-value BVA: 17, 18, 65, 66 (4 tests)
• 3-value BVA: 17, 18, 19, 64, 65, 66 (6 tests)

Most exam questions use 2-value BVA unless they specify 3-value. The Syllabus v4.0 covers both.

Exam trap: a common question asks "how many test cases for 2-value BVA on age 18-65?" — answer is 4 (17, 18, 65, 66). Do not confuse with "how many partitions in EP?" (3).

Worked Example 2: Decision Tables

Use when behavior depends on combinations of conditions. For N Boolean conditions, the complete decision table has 2^N columns.

Example — a discount rule: customer gets 10% off if they are a member AND their order > $100.

You test each column. Decision tables ensure complete coverage of condition combinations — a key advantage over ad-hoc testing.

Worked Example 3: State Transition Testing

Use when the system has distinct states and transitions between them.

Example — an ATM card:

• States: Valid, Invalid (PIN locked)
• Events: correct PIN, incorrect PIN (3 strikes rule)
• From Valid + "incorrect PIN (3rd time)" -> Invalid
• From Invalid + anything -> Invalid (no recovery without branch visit)

CTFL Syllabus v4.0 tests 0-switch coverage (every transition covered at least once) at the Foundation level.

Worked Example 4: Use Case Testing

Derive test cases from use case scenarios — the main success scenario plus alternate and exception flows. One test per flow at minimum. This is how you translate requirements-level use cases into executable test cases.

Experience-based Techniques

• Error guessing — tester hypothesizes likely defects (null inputs, zero, boundaries, concurrency)
• Exploratory testing — simultaneous test design, execution, learning; often session-based
• Checklist-based — testing guided by a predefined checklist

---

Chapter 5 — Managing the Test Activities (~24%)

The second-biggest chapter. Focuses on test planning, monitoring, risk, estimation, and defect management.

High-yield concepts:

• Test plan content — context, objectives, scope, schedule, estimates, risks, approach, resources, deliverables, entry/exit criteria
• Entry criteria — what must be true before testing starts (e.g., requirements baselined, test environment ready)
• Exit criteria (Definition of Done) — what must be true before testing stops (e.g., all planned tests executed, coverage reached, no outstanding critical defects)
• Test estimation techniques:
  • Ratio-based (e.g., 25% of dev effort goes to test)
  • Extrapolation from similar past projects (historical data)
  • Wideband Delphi / Planning Poker — expert consensus
  • Three-point estimation — optimistic, most likely, pessimistic
  • Burndown charts — for Agile iterations
• Risk-based testing — prioritize testing by risk level = likelihood x impact. High-risk items get more and earlier testing.
• Product risk vs project risk — product risk is about the software (usability, performance, security); project risk is about the project (schedule, staffing, tooling)
• Defect lifecycle (canonical flow):
  1. New — reported, not yet triaged
  2. Open/Assigned — confirmed and assigned to a developer
  3. In Progress — being fixed
  4. Fixed/Resolved — fix committed, awaiting verification
  5. Retested — tester verifies
  6. Closed — verified fixed (or deferred/rejected/duplicate) States can also include Reopened (fix did not work) and Rejected (not a defect).
• Defect report content — ID, title, date, author, severity, priority, steps to reproduce, expected vs actual, environment, attachments, status, history
• Communication — test reports, dashboards, stakeholder communication

Exam trap: conflating severity (technical impact of the defect) with priority (urgency of fixing it). A typo on the homepage can be low severity, high priority; a crash in a rarely used admin screen can be high severity, low priority.

---

Chapter 6 — Test Tools (~8%)

The smallest chapter. Covers tool classification, benefits, risks, and selection.

High-yield concepts:

• Tool classifications — management tools (test management, defect tracking), static testing tools (static analysis, review), test design & implementation tools, test execution tools (unit test frameworks, automation), non-functional tools (performance, security), DevOps tools (CI/CD)
• Benefits of automation — repeatability, speed, coverage breadth, early feedback
• Risks of automation — unrealistic expectations, underestimating maintenance cost, over-reliance, tool abandonment
• Tool selection — organizational readiness, pilot project, success factors (training, internal champions, adoption plan)

---

Cost & Registration via Your National Board

ISTQB is a federation of national boards. You register with the board in your country. In the US, that is ASTQB.

Always verify current pricing at astqb.org (or your national board) before registering — fees can change mid-year and training-partner bundles vary.

How to register (US / ASTQB path):

1. Go to astqb.org and create an account
2. Choose Certified Tester Foundation Level — v4.0
3. Select online proctored (Pearson VUE or other authorized) or in-person test center
4. Pay the fee ($229 USD — verify current)
5. Schedule your exam slot
6. On exam day, present a government-issued photo ID; follow proctor instructions; receive instant provisional results (official certificate within a few weeks)

---

No Expiration — But Specialist and Advanced Levels Await

CTFL is a lifetime credential. No renewal fee, no continuing education requirement. Once you pass, you can add the credential to LinkedIn and your resume permanently.

After CTFL, the Specialist Level tracks let you specialize:

And the Advanced Level deep-dives:

CTFL is a prerequisite for every Specialist and Advanced exam.

---

Build CTFL Mastery with FREE Practice Questions

Access FREE ISTQB CTFL Practice QuestionsPractice questions with detailed explanations

Train on scenario items across Syllabus v4.0 — including K3 application questions on equivalence partitioning, boundary value analysis, decision tables, and state transition — 100% FREE, with instant explanations.

---

4-6 Week CTFL Study Plan

This schedule assumes ~6-8 hours per week and zero prior formal testing experience. Compress to 3-4 weeks if you already have 6+ months of QA work experience.

Time Allocation Mirroring Syllabus v4.0 Weightings

---

Recommended CTFL Resources (Free + Paid)

Minimum free path to pass: Syllabus v4.0 PDF (read twice) + all 4 Sample Exams + our free CTFL practice bank. Total cost: $229 exam fee only.

---

Test-Taking Strategy — 90 Seconds per Question

60 minutes / 40 questions = 90 seconds per question on average. Non-native English speakers get 75 minutes (112.5 seconds per question). Here is how to manage the clock:

1. First pass (30 minutes) — answer every question you know in under 60 seconds. Flag anything that takes longer. Aim to answer ~30 questions confidently in round 1.
2. Second pass (20 minutes) — return to flagged items. Now you have ~2 minutes each to work through decision tables, BVA arithmetic, or state transition diagrams.
3. Third pass (10 minutes) — review any answers you were uncertain about. Do not change an answer unless you are confident the new choice is better.

K-level targeting — each Learning Objective is tagged K1 (remember), K2 (understand), or K3 (apply). K3 items take the longest because they require you to work through a calculation (how many test cases? which decision table column? what is the next state?). Save K3 items for the second pass if they slow you down on the first.

One answer per question — CTFL is single-best-answer multiple choice. No multi-select, no partial credit. If you must guess, eliminate obvious distractors first; a blind 1-of-4 guess has a 25% chance of scoring.

---

Common CTFL Pitfalls (And How to Avoid Them)

1. Confusing test design techniques. Equivalence partitioning vs boundary value analysis vs decision tables vs state transition — each has a specific trigger. EP: divide input domain. BVA: test at boundaries. Decision tables: behavior depends on combinations. State transition: system has states. Drill 30+ problems until this is automatic.
2. Missing the K-level targeting. K1/K2 items test recall/understanding — shorter stems. K3 items require you to compute an answer. Do not under-budget time for K3 items (there are typically 8-12 on the exam).
3. Confusing test levels with test types. Component/Integration/System/Acceptance are levels. Functional/Non-functional/White-box/Change-related are types. These are orthogonal dimensions and the Syllabus v4.0 will test you on the distinction.
4. Mixing severity and priority. Severity is about the defect's technical impact. Priority is about how urgently it should be fixed. They can be independent.
5. Forgetting 2-value vs 3-value BVA. The default in many textbooks is 2-value (boundary + one side = 4 tests for a bounded range). Syllabus v4.0 covers both; read each question carefully.
6. Misremembering the seven testing principles. Know them in order and know each phrase verbatim — "Testing shows the presence of defects, not their absence," "Exhaustive testing is impossible," etc.
7. Over-relying on real-world experience. Like PSM I, CTFL rewards literal Syllabus answers. If your workplace lets developers sign off on their own code, that is not the Syllabus v4.0 answer to "who should moderate an inspection."
8. Neglecting Chapter 6. It is only ~8% of the exam, but 3 questions is the margin between 65% and 57%. Spend at least 2 hours on it.

---

Career Value: QA Engineer Salary & Roles

CTFL is the entry-level credential that opens QA and SDET doors. 2026 US salary ranges (BLS and industry surveys):

Source: BLS Software QA Analysts and Testers (2026), Glassdoor, Levels.fyi industry data.

Career ladder after CTFL:

• Immediate next step — CTFL-AT (Agile Tester) if you work on Scrum teams, CTFL-PT (Performance) if you are interested in load testing, or CT-AI if you want to test AI/ML systems
• 12-24 months out — Advanced Level (CTAL-TA for Test Analysts, CTAL-TM for managers, CTAL-TTA for technical/automation-focused testers)
• Parallel credentials — ISTQB pairs well with Selenium/Playwright automation certs, AWS DevOps, Scrum.org PSM I (for Scrum-team QA roles), and Certified Agile Tester (CAT)

---

CTFL vs Competing Certifications

For 90%+ of candidates, CTFL is the right starting point because it is globally recognized, methodology-agnostic, and prerequisite to every ISTQB Specialist/Advanced credential.

---

Start Your FREE CTFL Prep Now

Begin FREE ISTQB CTFL Practice QuestionsPractice questions with detailed explanations

Join candidates preparing with OpenExamPrep's 100% FREE CTFL practice platform, built around Syllabus v4.0 and refreshed continuously for 2026.

---

Official Sources Used

• ISTQB Certified Tester Foundation Level Syllabus v4.0 (April 2023, current 2026) — istqb.org/certifications/certified-tester-foundation-level
• ISTQB Sample Exams A, B, C, D (free, v4.0) — istqb.org
• ISTQB Glossary — glossary.istqb.org
• ASTQB — astqb.org (US national board, 2026 pricing)
• BLS Software Quality Assurance Analysts and Testers — Occupational Outlook Handbook, 2026
• Glassdoor and Levels.fyi — 2026 QA and SDET salary data
• Lisa Crispin & Janet Gregory — Agile Testing Quadrants (referenced by Syllabus v4.0 Chapter 2)
• Mike Cohn — Test Automation Pyramid (referenced by Syllabus v4.0 Chapter 2)

Certification details, syllabus versions, and fees may change. Always confirm current requirements directly on istqb.org and your national board (astqb.org for US candidates) before registering.