ISTQB Foundation Level learning objectives
Summary
The ISTQB Foundation Level syllabus v4.0.1 contains 64 learning objectives distributed across six chapters. Each one is tagged with a cognitive level: K1 (remember), K2 (understand), or K3 (apply). The level tells you how the exam will test that topic. A K1 topic requires recall. A K2 topic requires explanation or comparison. A K3 topic requires applying a procedure to a scenario.
All content in Chapters 1 through 6 is examinable at K1 as a baseline, meaning you may be asked to recall any keyword from any chapter even if it is not listed as a separate learning objective. Each chapter also opens with a keyword list that the syllabus explicitly calls out as examinable.
K-level summary
| K-level | Label | What it requires on the exam |
|---|---|---|
| K1 | Remember | Recognize or recall a term, fact, or basic idea |
| K2 | Understand | Explain, compare, classify, summarize, or distinguish between related concepts |
| K3 | Apply | Use a specified procedure or technique when given a scenario or a set of inputs |
K3 objectives tend to produce the most time-consuming exam questions because they usually include a short scenario, a code fragment, a decision table, or a state diagram that you have to work through. Equivalence partitioning, boundary value analysis, decision table testing, and state transition testing are all K3.
Chapter 1: Fundamentals of Testing - 8 exam questions
| Learning objective | K-level | Topic |
|---|---|---|
| FL-1.1.1 | K1 | Identify typical test objectives |
| FL-1.1.2 | K2 | Distinguish between testing and debugging |
| FL-1.2.1 | K2 | Explain why testing is necessary |
| FL-1.2.2 | K1 | Recall the relationship between testing and quality assurance |
| FL-1.2.3 | K2 | Distinguish between errors, defects, failures, and root causes |
| FL-1.3.1 | K2 | Explain the seven testing principles |
| FL-1.4.1 | K2 | Summarize the test activities and tasks in the test process |
| FL-1.4.2 | K2 | Explain the impact of context on the test process |
| FL-1.4.3 | K2 | Distinguish between testware types produced in different test activities |
| FL-1.4.4 | K2 | Explain the value of maintaining traceability |
| FL-1.5.1 | K2 | Compare the test manager and tester roles |
| FL-1.6.1 | K2 | Identify the skills required for testing |
| FL-1.6.2 | K1 | Recall the advantages of the whole team approach |
| FL-1.6.3 | K2 | Distinguish between the benefits and drawbacks of independence in testing |
Chapter 1 is all K1 and K2. There are no K3 objectives here, so the work is understanding and explaining rather than applying procedures. This chapter also introduces the vocabulary used in every later chapter, so it is worth taking seriously even if the K-levels look manageable.
Chapter 2: Testing throughout the software development lifecycle - 6 exam questions
| Learning objective | K-level | Topic |
|---|---|---|
| FL-2.1.1 | K2 | Explain how testing adapts to different SDLC models |
| FL-2.1.2 | K1 | Recall good testing practices for any SDLC model |
| FL-2.1.3 | K1 | Recall why test-first approaches support early testing |
| FL-2.1.4 | K1 | Recall what DevOps is and its relationship to testing |
| FL-2.1.5 | K1 | Recall the concept of shift left in testing |
| FL-2.1.6 | K1 | Recall the purpose of retrospectives in testing |
| FL-2.2.1 | K2 | Distinguish between the five test levels |
| FL-2.2.2 | K2 | Distinguish between the four test types |
| FL-2.2.3 | K2 | Distinguish between confirmation testing and regression testing |
| FL-2.3.1 | K2 | Summarize the triggers, scope, and types of maintenance testing |
Chapter 2 mixes several K1 objectives (DevOps, shift left, retrospectives, test-first) with K2 objectives on test levels, types, and lifecycle models. The K1 objectives are worth a few minutes each. The K2 objectives on test levels versus test types deserve more attention because distinguishing between them is a common source of exam errors.
Chapter 3: Static testing - 4 exam questions
| Learning objective | K-level | Topic |
|---|---|---|
| FL-3.1.1 | K1 | Identify work products examinable by static testing |
| FL-3.1.2 | K2 | Explain the value of static testing |
| FL-3.1.3 | K2 | Distinguish between static testing and dynamic testing |
| FL-3.2.1 | K1 | Recall the benefits of early and frequent stakeholder feedback |
| FL-3.2.2 | K2 | Explain the activities in a review process |
| FL-3.2.3 | K1 | Compare the roles and responsibilities in reviews |
| FL-3.2.4 | K2 | Compare review types |
| FL-3.2.5 | K1 | Recall the success factors for reviews |
Chapter 3 has no K3 objectives. Study the four review types and be able to distinguish them from each other. Inspection is the most formal. Informal review is the least. Walkthrough and technical review sit between them and are the most commonly confused pair.
Chapter 4: Test analysis and design - 11 exam questions
| Learning objective | K-level | Topic |
|---|---|---|
| FL-4.1.1 | K2 | Explain the categories of test techniques and their uses |
| FL-4.2.1 | K3 | Apply equivalence partitioning to derive test cases |
| FL-4.2.2 | K3 | Apply boundary value analysis to derive test cases |
| FL-4.2.3 | K3 | Apply decision table testing to derive test cases |
| FL-4.2.4 | K3 | Apply state transition testing to derive test cases |
| FL-4.3.1 | K2 | Explain statement testing and statement coverage |
| FL-4.3.2 | K2 | Explain branch testing and branch coverage |
| FL-4.3.3 | K2 | Explain the value of white-box testing |
| FL-4.4.1 | K2 | Explain error guessing |
| FL-4.4.2 | K2 | Explain exploratory testing |
| FL-4.4.3 | K2 | Explain checklist-based testing |
| FL-4.5.1 | K1 | Recall collaborative user story writing approaches |
| FL-4.5.2 | K2 | Summarize how to write acceptance criteria |
| FL-4.5.3 | K2 | Explain acceptance test-driven development (ATDD) |
Chapter 4 has the most learning objectives and the most K3 objectives on the exam. The four black-box techniques (equivalence partitioning, boundary value analysis, decision table testing, state transition testing) all require application, meaning exam questions will give you a scenario and ask you to derive or evaluate test cases. Working through examples before the exam is the most reliable preparation for this chapter.
Chapter 5: Managing the test activities - 9 exam questions
| Learning objective | K-level | Topic |
|---|---|---|
| FL-5.1.1 | K2 | Identify the purpose and content of a test plan |
| FL-5.1.2 | K1 | Recall how testers contribute to iteration and release planning |
| FL-5.1.3 | K1 | Identify entry criteria and exit criteria |
| FL-5.1.4 | K3 | Apply estimation techniques for test effort |
| FL-5.1.5 | K1 | Recall the purpose of test case prioritization |
| FL-5.1.6 | K2 | Summarize the test pyramid concept |
| FL-5.1.7 | K2 | Summarize the quadrants in the testing quadrants model |
| FL-5.2.1 | K1 | Identify product risks and project risks |
| FL-5.2.2 | K2 | Explain how risk analysis and risk control affect testing |
| FL-5.2.3 | K2 | Explain how product risk analysis may influence thoroughness and test scope |
| FL-5.2.4 | K2 | Explain what measures can be taken in response to analyzed product risks |
| FL-5.3.1 | K1 | Recall metrics used for testing and quality evaluation |
| FL-5.3.2 | K2 | Summarize the purpose of test reports |
| FL-5.3.3 | K2 | Exemplify how to communicate test status |
| FL-5.4.1 | K2 | Explain how configuration management supports testing |
| FL-5.5.1 | K3 | Apply a procedure for writing a defect report |
Chapter 5 has two K3 objectives: effort estimation and writing a defect report. Both are procedural. For estimation, know how to use estimation by analogy and expert-based estimation. For defect reports, know the standard contents: defect title, severity, status, environment, steps to reproduce, expected result, actual result, and supporting materials. The rest of Chapter 5 is K1 and K2, covering planning, risk, monitoring, and configuration management.
Chapter 6: Test tools - 2 exam questions
| Learning objective | K-level | Topic |
|---|---|---|
| FL-6.1.1 | K2 | Explain how test tools support testing |
| FL-6.2.1 | K1 | Recall the benefits and risks of test automation |
Chapter 6 has only two learning objectives and two exam questions. Both are K1 and K2. Know the categories of test tools and what each supports. Know the benefits of automation (consistency, repeatability, reduced manual effort) and the risks (maintenance cost, false confidence, setup investment). This chapter is short to study if you do not overthink it.
How to use the K-levels when studying
The K-level is a reliable guide to how much time a topic deserves. K1 topics need a definition and a few recall checks. K2 topics need enough understanding to explain the concept and distinguish it from related concepts. K3 topics need worked examples: use the official sample exams, identify which technique a question is testing, and practice applying the procedure to different inputs until it becomes automatic.
When you get a practice question wrong, check the K-level of the relevant learning objective. If it was K3 and you only studied the definition, the fix is examples. If it was K1 and you still missed it, the fix is more deliberate recall practice with the glossary.
Last reviewed: June 2026.