LEARN. PRACTICE. GROW.ISTQB Foundation: testing and quality decisions
Learn to design tests, interpret coverage, and assess release risk through exercises and fictional banking scenarios.
Objectives and progression
Six original modules cover fundamentals, the development lifecycle, static review, case design, test management, and tools. Includes 30 questions and five fictional cases about transfers, shared libraries, international requirements, release risk, and unstable pipelines. Official CTFL chapters are mapped; introductory practice does not claim full exam coverage or distribution. The internal assessment reuses 23 bank decisions. Consulted official documentation identifies CTFL v4.0, syllabus v4.0.1, and exam structure v1.19. Text and exercises are original and do not reproduce official questions.
Audience: Beginning testers, project managers, developers, and support staff involved in release quality.
Prerequisites: General familiarity with applications and development; exercises require neither programming nor production access.
195 estimated study minutes
- Distinguish evidence, coverage, defects, and risk.
- Select test levels, types, and techniques for a change.
- Design cases using boundaries, combinations, and states.
- Report results and assess confidence in the pipeline.
Modules
- Evidence, defects, and test objectives
- Lifecycle testing and regression
- Review before code
- Design cases and measure coverage
- Risk, defects, and release decisions
- Tools and confidence in the signal
Continue learning
References and version
CTFL v4.0; syllabus v4.0.1 (2024-09-15)
- ISTQB CTFL v4.0 certification overview · 2026-09-29
- ISTQB CTFL syllabus v4.0.1 · 2026-09-29
- ISTQB Exam Structures & Rules Tables · 2026-09-29
- ISTQB Exam Structures and Rules · 2026-09-29
- ISTQB CTFL v4.0 FAQ · 2026-09-29
What you will explore
0 / 6Evidence, defects, and test objectives
Interpret results without confusing passing tests with absence of risk.
Lifecycle testing and regression
Select test levels and types according to the change and dependencies.
Review before code
Detect ambiguities and defects in work products without executing them.
Design cases and measure coverage
Apply partitions, boundaries, decisions, states, and structural coverage.
Risk, defects, and release decisions
Turn results into useful information for an accountable decision.
Tools and confidence in the signal
Assess automation by the evidence it produces and the effort to maintain it.