ISTQB CTFL 2018: What the Retired v3.1 Exam Taught and What Replaced It

CTFL 2018, commonly associated with syllabus v3.1, is now a retired ISTQB Foundation exam. English accredited training, exams, and retakes ended on 9 May 2024, and other-language versions ended on 9 November 2024. Candidates cannot use the old syllabus as the basis for a new v3.1 exam in 2026; the current route is CTFL v4.0.

Retirement of the exam did not invalidate certificates already earned. ISTQB states that holders of previous Foundation versions remain certified. That distinction is important: an existing CTFL 2018 certificate can still satisfy Foundation prerequisites where a valid Foundation certificate is required, even though the old exam itself is no longer available.

The retired exam historically used the familiar 40-question, 40-point format with a passing score of 26 and a standard duration of 60 minutes. Its subject matter remains useful background because many core concepts persist, but current candidates should not assume that a 2018 course maps cleanly to the rewritten v4.0 learning objectives.

CTFL 2018 established a common testing vocabulary across roles

The v3.1 syllabus introduced testing fundamentals, reasons for testing, principles, the test process, and the psychology of testing. That vocabulary helped testers, developers, managers, and business participants discuss defects, failures, coverage, independence, and objectives with fewer hidden assumptions.

A core lesson was that testing and debugging are different activities. Testing provides information and can reveal failures; debugging identifies and removes causes. Another was that testing is context-dependent: the same process cannot be applied mechanically to every product, lifecycle, risk profile, or organization.

Those ideas remain valuable because terminology supports collaboration. Even when a team uses lightweight practices, shared definitions make it easier to discuss what was reviewed, which behavior was exercised, what evidence exists, and what uncertainty remains.

The 2018 syllabus organized testing across lifecycle, levels, and types

CTFL v3.1 covered software development lifecycle models, test levels, test types, and maintenance testing. Candidates learned to distinguish component, integration, system, and acceptance perspectives and to recognize that functional and non-functional testing can occur at different levels.

The syllabus also emphasized that testing activities should be adapted to the lifecycle. Sequential and iterative models create different timing and collaboration needs. Even before v4.0 expanded modern delivery emphasis, Foundation study was intended to be applicable across more than one development approach.

Maintenance testing addressed changes to existing systems: fixes, enhancements, migrations, platform changes, and retirement activities can all create risk. Regression testing and impact analysis help determine what existing behavior may be affected by change.

Static testing and reviews were already part of the Foundation model

The retired syllabus treated review as a way to find defects without executing the product. Requirements, designs, code, test cases, and other work products can all contain ambiguity, inconsistency, omissions, and errors that are cheaper to correct before they propagate.

Review roles and processes varied by formality, but preparation focused on why review works, what makes it effective, and how feedback should be handled. The psychology of testing mattered because poorly communicated findings can create defensiveness and reduce the value of technically correct observations.

These concepts still transfer to current testing. Modern teams may call the activity peer review, refinement, three-amigos discussion, or pull-request review, but the underlying idea is the same: use diverse perspectives to discover problems before later testing has to detect their consequences.

Test techniques gave candidates systematic alternatives to intuition

CTFL 2018 covered black-box, white-box, and experience-based techniques. Equivalence partitioning and boundary value analysis structured input domains; decision tables handled interacting conditions; state transitions modeled history-dependent behavior; statement and decision coverage examined implementation structure.

Experience-based testing recognized that tester knowledge can find issues not captured by formal specifications. Error guessing, exploratory approaches, and checklists draw on domain understanding and defect patterns. The important lesson was that no single technique provides complete coverage.

Those techniques remain relevant under v4.0, but current candidates should follow the current syllabus wording, learning objectives, and examples. Older notes can reinforce fundamentals, yet version-specific exam preparation should be anchored in current material so subtle changes are not missed.

Test management in v3.1 covered planning, risk, progress, and defects

Foundation candidates studied test organization, planning and estimation, monitoring and control, configuration management, risk, and defect management. The goal was to understand why testing needs coordination and how evidence supports project decisions, not to turn entry-level testers into full test managers.

Risk thinking was especially important because exhaustive testing is impossible. Product risks influence which areas receive more testing, while project risks can threaten the ability to complete testing at all. Prioritization is therefore a rational response to constraints rather than a sign that lower-priority behavior is unimportant.

Defect reports were treated as communication artifacts. Reproducibility, observed and expected behavior, environment, severity, and supporting evidence help teams act efficiently. That remains a practical skill regardless of which Foundation syllabus version a tester originally studied.

The v4.0 rewrite changed the preparation target, not the validity of old certificates

ISTQB released CTFL v4.0 in May 2023 and described it as a rewrite from scratch rather than a simple combination of the former Foundation and Agile Tester syllabi. The new version keeps essential testing knowledge but updates objectives for contemporary cross-functional delivery and integrates Agile-related concepts more directly.

The sunset period gave training providers and candidates time to move. English v3.1 availability ended in May 2024 and other languages in November 2024. By 2026 there is no ambiguity about which version a new candidate should study: the active Foundation syllabus is v4.0, currently published as v4.0.1 on the certification page.

Holders of an older Foundation certificate do not need to retake solely because the syllabus retired. They may still choose to study the current Foundation certification material to refresh modern terminology or prepare for an Advanced or Specialist path, but that is different from saying their earlier achievement expired.

Use 2018 material as history and reinforcement, not as a current exam map

Older textbooks, courses, flashcards, and question sets can still explain durable concepts, especially test principles, lifecycle relationships, reviews, design techniques, risk, and defects. Their weakness is version alignment. A candidate may spend time memorizing terminology, learning objectives, or emphasis that no longer matches the exam being delivered.

A sensible approach is to start with the current syllabus and use older material only when it clarifies a concept that still appears. When wording differs, the current ISTQB source should win. This avoids the common mistake of mixing two versions into one study plan and assuming that broad conceptual overlap means the exam scope is identical.

CTFL 2018 remains significant because many practicing testers earned their Foundation credential under it and because its core ideas continue to influence the scheme. Its status, however, is historical. New preparation should move forward to v4.0 while respecting that existing v3.1 certificate holders remain part of the same certification pathway.

Comparing v3.1 with v4.0 helps experienced holders update without discarding useful knowledge

People who earned CTFL under the 2018 syllabus do not need to relearn testing from the beginning. The durable core—testing principles, lifecycle relationships, reviews, design techniques, risk, defects, and tools—still provides a strong base. The useful task is to identify where current terminology, collaboration expectations, and learning objectives have changed so old mental models do not become a source of confusion.

For example, modern Foundation material places stronger emphasis on cross-functional collaboration and integrates contemporary lifecycle practices more directly. Experienced holders may already work this way even if their original exam did not emphasize it in the same structure. Updating knowledge can therefore be a mapping exercise between current practice and the new syllabus rather than a complete restart.

Organizations should also be careful when they maintain internal training based on old slides. A certificate can remain valid while training content becomes outdated. New staff preparing for CTFL should receive v4.0-aligned material, and internal terminology should be reviewed so teams are not taught an obsolete exam structure simply because historical courseware is convenient.

Archived question banks deserve similar caution. Some questions still test enduring concepts, but others may reflect old wording, retired learning objectives, or emphasis that has shifted. They are best used as supplemental practice only after the current syllabus has established what is in scope. The current sample exams are a safer reference for exam style and version-specific expectations.

CTFL 2018 should therefore be treated with two kinds of respect: respect for the certificate that people legitimately earned, and respect for version history when guiding new candidates. Conflating retirement with invalidation is wrong, but pretending nothing changed is also wrong. The clean message is that v3.1 certificates remain valid while v4.0 is the current examination and study path.

For teams with many v3.1 certificate holders, a short internal update can be more useful than asking everyone to recertify. Reviewing the v4.0 release changes, current terminology, collaboration concepts, and any techniques that have shifted helps experienced testers stay aligned with colleagues preparing under the new syllabus. That preserves the value of earlier certification while keeping day-to-day practice current.

The same principle applies to recruitment and role descriptions. Requiring “current CTFL” should not accidentally exclude someone whose valid Foundation certificate was earned under v3.1 when the role only needs the credential. If a job specifically requires familiarity with v4.0 content, that expectation should be stated separately. Clear wording respects the certification rules while still allowing employers to ask for up-to-date knowledge where it matters.

That distinction keeps historical certification value separate from current syllabus readiness and avoids unnecessary confusion for experienced testers.

ExamSnap's ISTQB CTFL-AT Practice Test Questions and Exam Dumps, study guide, and video training course are complicated in premium bundle. The Exam Updated are monitored by Industry Leading IT Trainers with over 15 years of experience, ISTQB CTFL-AT Exam Dumps and Practice Test Questions cover all the Exam Objectives to make sure you pass your exam easily.