CTFL Domain 2: Testing Throughout the Software Development Lifecycle (15%) - Complete Study Guide 2026

What Domain 2 Covers on the CTFL Exam

Testing Throughout the Software Development Lifecycle is the second of six domains in the ISTQB Certified Tester Foundation Level syllabus (CTFL v4.0.1, dated 2024-09-15). It accounts for 15% of the exam content, which on a 40-question, 40-point exam translates to approximately six questions. That's smaller than Test Analysis and Design (27.5%), the largest domain, but it's far from trivial - every question you drop here still counts against the 26-of-40 passing threshold.

This domain asks you to connect testing activities to the broader software development process. Instead of memorizing testing techniques in isolation, you need to understand when each activity happens, who performs it, and how the lifecycle model in use shapes the testing approach. If you haven't yet reviewed how this domain relates to the other five, the CTFL Exam Domains 2026 guide breaks down all six content areas side by side.

Software Development Models and Where Testing Fits

The CTFL syllabus expects you to compare sequential development models against iterative and incremental ones, and to explain how testing activities map onto each.

Exam questions in this area often present a short scenario ("a team delivers working software every two weeks") and ask which lifecycle model is being described, or what testing implication follows from it. You're not expected to write Agile ceremonies from memory, just to recognize the testing consequences of each model choice.

The Four Test Levels You Must Know Cold

This is the single highest-value subtopic in Domain 2. The syllabus defines four distinct test levels, each with its own objectives, test basis, and typical test object.

Expect exam questions that describe a test activity in a scenario and ask you to identify the correct test level, or that ask you to distinguish component integration testing from system integration testing. The distinction between "verifying interfaces between components" versus "verifying the system as a whole" is a classic trap.

Test Types: Functional, Non-Functional, and Beyond

Domain 2 also covers test types - categories of testing grouped by the specific objective being tested, independent of which test level they're performed at. The syllabus groups these into four categories:

• Functional testing: what the system does - evaluates functions the system performs against specified requirements
• Non-functional testing: how well the system performs - includes performance, usability, reliability, and security characteristics
• Black-box testing: based on specifications, without reference to internal structure
• White-box testing: based on the internal structure or implementation of the software

A recurring exam trap is confusing test types with test levels. Functional testing, for example, can be performed at any of the four test levels - it isn't tied exclusively to system testing. Similarly, non-functional testing can occur at the component level (e.g., component-level performance checks) even though people intuitively associate it only with full-system evaluation.

Maintenance Testing and Change Impact

Maintenance testing is one of the more overlooked subtopics in this domain, yet it's explicitly part of the syllabus. It covers testing performed on an existing system after it's already in production, triggered by:

• Modification (bug fixes, enhancements, upgrades)
• Migration (moving to a new platform or environment)
• Retirement (decommissioning a system, including data archiving considerations)

Closely tied to maintenance testing is impact analysis - evaluating the changes made to determine which parts of the existing system may have been affected and therefore need re-testing. Candidates often underestimate this section because it feels administrative rather than technical, but it's a reliable source of one or two exam questions.

How Domain 2 Questions Are Actually Worded

Every CTFL exam question is multiple-choice, drawn from a pool aligned to the CTFL v4.0.1 syllabus. Domain 2 questions tend to follow a few recognizable patterns rather than pure definition recall:

1. Scenario-to-test-level mapping: A short paragraph describes an activity (e.g., "testers check that the payment module correctly calls the shipping API"), and you select the matching test level.
2. Model comparison: A description of a project's delivery cadence, and you identify whether it reflects a sequential or iterative approach, plus the testing implication.
3. Definition discrimination: Two closely related terms (confirmation vs. regression testing, or component vs. integration testing) with answer options designed to catch a partial understanding.
4. Trigger identification: A scenario describing a production change, asking whether it calls for maintenance testing and what kind of impact analysis is needed.

None of these require deep technical or coding knowledge - they test whether you can apply vocabulary correctly to a described situation, which is consistent with the exam's overall Foundation Level design. If you're unsure how this compares in difficulty to the rest of the exam, the How Hard Is the CTFL Exam guide walks through difficulty by domain.

Where Domain 2 Fits in a Full Study Plan

Because Domain 2 is only 15% of the exam, it shouldn't consume a disproportionate share of your prep time - but it also shouldn't be crammed into a single evening. A practical way to sequence it is to study it right after Domain 1: Fundamentals of Testing, since the two domains share vocabulary (test process, test basis, testing objectives) that reinforces retention.

For a complete week-by-week plan covering all six domains, not just this one, see the CTFL Study Guide 2026. You can also run timed domain-specific quizzes on our CTFL practice test platform to see exactly where your Domain 2 knowledge is weakest before exam day.

Common Mistakes Candidates Make on This Domain

• Treating test levels as interchangeable with test phases in your own workplace. Real-world job titles and processes don't always map cleanly to syllabus definitions - answer based on the syllabus, not your employer's terminology.
• Assuming non-functional testing only happens at system or acceptance level. It can be planned at any test level; the syllabus explicitly avoids limiting it to "the end."
• Confusing confirmation testing with regression testing on scenario questions where a defect fix is described.
• Skipping maintenance testing entirely because it feels like a minor topic - it still generates scoreable questions.
• Ignoring the Agile/iterative model implications and only studying the V-model, since many current test teams work in iterative environments and the syllabus reflects that.

Registration, Fees, and Exam Logistics

Domain 2 is tested within the same single exam as the other five domains - there's no separate exam per domain. A few logistics worth confirming before you register:

• The exam is governed by ISTQB, with ASTQB serving as the U.S. member board and AT*SQA as the ASTQB-affiliated exam provider.
• The exam fee through AT*SQA is $229 USD.
• You get 40 multiple-choice questions worth 40 points total, with a 60-minute time limit (75 minutes for approved non-native-language candidates).
• The passing score is 26 of 40, or 65%.
• There are no prerequisites to sit the exam.
• You can take the exam via online webcam-proctored testing or in person at a Kryterion test center.
• Once earned, the certificate is valid for life - no renewal or continuing education is required.

For a full breakdown of what that $229 fee includes and any related costs like training or retakes, see the CTFL Certification Cost 2026 guide. And if you're still deciding whether the certification is worth pursuing at all given the investment, the Is the CTFL Certification Worth It analysis covers the ROI question directly, while the CTFL Salary Guide 2026 looks at how certification connects to compensation.

Frequently Asked Questions