ISTQB Foundation 4.0: an evolution closer to modern practices.

In a context where product teams are shipping faster and faster, QA no longer has the luxury of being just a simple “safety net” at the end of the chain. ISTQB has clearly understood this and has evolved its Foundation syllabus towards a 4.0 version that is much closer to modern practices: Agile, DevOps, automation, continuous testing, and stronger collaboration with the rest of the team.

Beyond a simple content update, this new version clarifies the tester’s role and aligns the certification with what is actually happening in today’s projects.

Reminder: what is ISTQB and what is the Foundation for?

ISTQB (International Software Testing Qualifications Board) defines an international framework of skills and certifications around software testing. The Foundation level (CTFL) is the baseline, intended for anyone who wants to master the fundamentals of testing: concepts, vocabulary, process, techniques, and the positioning of testing within the software lifecycle.

This certification is designed to be applicable to all contexts (Agile, V‑Model, DevOps, etc.) and to provide a common language for testers, developers, Product Owners, managers, and business stakeholders. This “shared reference” aspect explains why many companies still require it or value it in QA career paths.

The main changes in the ISTQB Foundation v4.0 syllabus

Version 4.0 of the Foundation syllabus is not just a light refresh of the 2018 document; it has been almost completely rewritten to better reflect current realities. The changes can be grouped into a few main themes.

1. Clear alignment with Agile and DevOps

The new syllabus integrates Agile and DevOps contexts much more explicitly, whereas the previous version treated them more as an “add‑on”. It now includes:

• An enriched vocabulary around ATDD, BDD, CI/CD, continuous testing, shift‑left, etc.

• A clearer positioning of the tester within an Agile team (collaboration with devs, PO, business, etc.).

• The idea that testing is no longer a phase, but a continuous activity throughout the lifecycle.

For QA professionals, this means the certification is no longer centered on an “academic V‑Model”, but takes into account the reality of teams that ship frequently with continuous integration and delivery pipelines.

2. Greater focus on practice and real situations

Syllabus 4.0 puts more emphasis on the ability to apply concepts, not just recite definitions. The content and learning objectives are designed so that testers can:

• Link test techniques to real project situations.

• Understand how to contribute to risk management, reviews, and continuous improvement.

• Use testing and automation tools within a coherent framework, even though the certification remains focused on concepts rather than on specific tools.

The authors of the syllabus even mention having followed a “test‑first” approach: defining the objectives and exam questions first, then writing the content accordingly, to guarantee the testability of each objective.

3. Risk‑based, exploratory, and performance testing brought to the forefront

Among the most visible changes, version 4.0 highlights approaches that have long been used in the field but were not detailed in previous versions:

• Risk‑based testing, to help prioritize what to test first and to what level of depth.

• Exploratory testing, seen as a technique in its own right, complementary to scripted tests.

• Performance testing, at least in its principles, to raise awareness of load, response time, and scalability issues.

This shift supports a QA role that is no longer limited to “executing test cases”, but helps drive the test strategy in line with business and technical priorities.

4. A more compact but more targeted syllabus

Several analyses show that the new English syllabus is shorter in page count than the 2018 version (for example, 74 pages vs. 93), while adding more recommended training time. This may sound paradoxical, but the goal is to reduce verbosity while keeping the essentials:

• Less redundancy, more clarity on learning objectives.

• A reworked chapter structure (static testing, test techniques, managing testing activities, tools, etc.).

• More detailed objectives around collaboration, experience‑based testing, test design, and analysis.

For learners, this results in a more readable document, but one that requires a better understanding of the links between chapters rather than just skimming definitions.

5. A stronger emphasis on collaboration and static testing

The syllabus also shines more light on often underestimated activities such as reviews, static testing, and collaboration around artifacts (user stories, specifications, mockups, etc.). It highlights:

• The role of reviews as a lever for improving quality upstream (shift‑left).

• The importance of communication between testers, devs, and stakeholders when defining tests.

• The promotion of a collaborative test‑based approach to deriving test cases.

This “teamwork” dimension clearly reflects the reality of agile projects and digital products, where QA is no longer a silo.

What this concretely changes for QA

Beyond the documentation, the key question remains: what does this new version change for testers, QA engineers, and, more broadly, product teams?

1. A certification more aligned with day‑to‑day team life

For testers already working in Agile/DevOps environments, the CTFL v4.0 content will better reflect their daily reality: user stories, CI/CD pipelines, automation, collaboration with developers, etc. It introduces notions of continuous testing and shared quality, rather than just a “test phase at the end of the project”.

This makes the certification more credible internally: taking CTFL 4.0 is no longer just about revising an outdated theoretical model, but about updating your knowledge against a framework consistent with current practices.

2. A stronger basis for discussing test strategy and risk

With the emphasis on risk‑based testing, exploratory testing, and performance, QA professionals now have a richer vocabulary to discuss test strategy with Product Owners, Product Managers, and managers. This helps, for example, to:

• Explain why efforts are focused on certain scenarios.

• Argue for the need to conduct reviews or invest in non‑functional testing.

• Better frame the scope of automation and what should remain exploratory.

This increased focus on risk and strategy supports a QA role that is more of a quality partner than a simple executor.

3. An impact on exam preparation

In terms of format, the exam remains a one‑hour paper with 40 multiple‑choice questions and a passing score of 65% (26 correct answers). It is still a closed‑book exam with no supporting material allowed.

However, the nature of the questions and learning objectives now relies more on understanding and application than pure memorization. Candidates need to be able to:

• Apply test techniques (black‑box, white‑box, experience‑based) to concrete examples.

• Relate test types and levels to the development lifecycle.

• Identify appropriate approaches for Agile or DevOps contexts.

This encourages preparation that is more scenario‑based than simple cramming of definitions.

Should you start training on the new syllabus now, and for whom?

For testers and QA already in role :

If you already work in a QA or product team, taking or retaking the certification based on the v4.0 syllabus can be beneficial in several ways:

• Updating your vocabulary and view of testing in line with current practices.

• Structuring concepts you may already be applying implicitly (risk, exploratory testing, collaboration).

• Sending a clear signal to your current or future employer about your baseline level and willingness to stay up to date.

For people retraining or early in their career :

For those entering QA, CTFL v4.0 remains an excellent entry point:

• It covers the fundamentals of the role with a standard, internationally recognized vocabulary.

• It is now better aligned with Agile environments, which are very common in companies.

• It opens the path to advanced levels (Test Analyst, Test Manager, etc.), which are also being aligned to v4.0.

For companies and managers :

For organizations, relying on the v4.0 syllabus helps to:

• Standardize the baseline QA level, especially in distributed or multicultural teams.

• Structure upskilling paths (onboarding, training plans, internal academies).

• Connect existing practices (Agile, DevOps, automation) with an external, recognized framework.

Conclusion

With version 4.0 of its Foundation syllabus, ISTQB is sending a clear message: software testing is no longer just a final quality gate, but an integrated, continuous, and collaborative activity at the heart of product challenges.

For testers, this is an opportunity to refresh their knowledge and strengthen their position as key players in quality strategy rather than mere “gatekeepers”.

For companies, it is a chance to revisit their QA training paths and align them with a framework that speaks as much about Agile, DevOps, and risk as it does about traditional test techniques.