Two weeks is a tight timeline for ISTQB Foundation Level, but it's realistic — especially if you have a software background and you're not starting from zero. This plan assumes roughly 1–2 hours of focused study per day, which is about 20–25 hours total.
If you have more time, spread it out. If you have less, cut the lighter chapters and double down on the high-weight ones.
What You Need Before You Start
- The ISTQB CTFL Syllabus 2023 — download it free from istqb.org. This is the official source of truth.
- A practice question bank — istqbexam.com has 423 official questions, free.
- A quiet hour each day — seriously. Scattered 10-minute sessions don't work for this.
The 14-Day Plan
Days 1–2: Chapter 1 — Fundamentals of Testing
This is the heaviest conceptual chapter and the one most people underestimate.
What to cover:
- Why testing exists (and why it's not the same as debugging)
- The 7 testing principles — memorize all of them
- The test process: planning, monitoring, analysis, design, implementation, execution, completion
- Testware: what it is, what it includes
- Testing roles: tester vs. test manager vs. developer
Day 1: Read through the chapter. Take notes. Day 2: Go back through your notes, then do 15–20 practice questions on Chapter 1. Review every wrong answer.
K-level focus: Heavy K2. You need to understand and recognize examples of each principle, not just name them.
Days 3–4: Chapter 2 — Testing Throughout the Software Development Lifecycle
This chapter is about when testing happens, not how.
What to cover:
- Different SDLC models (sequential, iterative, incremental) and their testing implications
- The shift-left approach
- Test levels: unit, integration, system, acceptance
- Test types: functional, non-functional, structural, change-related
- Maintenance testing (why and when)
Day 3: Read + notes. Day 4: Practice questions. Pay special attention to which test level catches which type of defect — this comes up often.
Days 5–6: Chapter 3 — Static Testing
Many candidates skip this chapter thinking it's minor. It's not.
What to cover:
- Static testing vs. dynamic testing
- Reviews: informal, walkthrough, technical review, inspection
- Roles in a formal review (moderator, author, reviewer, scribe, manager)
- Static analysis tools and what they find
Day 5: Read + notes. The review process and roles are worth memorizing precisely. Day 6: Practice questions. Focus especially on when to use which review type.
Days 7–9: Chapter 4 — Test Analysis and Design (3 days)
This is the most technical chapter and the most likely source of K3 questions on your exam. Give it three days.
What to cover:
- Black-box techniques: Equivalence Partitioning (EP), Boundary Value Analysis (BVA), Decision Tables, State Transition Testing, Use Case Testing
- White-box techniques: Statement coverage, Branch/Decision coverage
- Experience-based techniques: Error guessing, Exploratory testing, Checklist-based testing
- Coverage criteria and how to calculate them
Day 7: EP and BVA — do multiple exercises, not just reading. Day 8: Decision tables and State Transition Testing — build tables from scratch. Day 9: White-box coverage + experience-based techniques + practice questions across the full chapter.
K-level focus: K3 for the design techniques. You will be given a spec and asked to derive test cases. Practice this hands-on.
Day 10: Chapter 5 — Managing the Test Activities
This chapter is more managerial in tone.
What to cover:
- Test planning: purpose, scope, content of a test plan
- Risk-based testing: product risk vs. project risk
- Test monitoring and control: metrics, progress reports
- Configuration management and its role in testing
- Defect management: the defect lifecycle
Read, take notes, do practice questions in one session. This chapter is heavy on definitions (K1/K2 dominant).
Day 11: Chapter 6 — Test Tools
Shortest chapter, but don't skip it entirely.
What to cover:
- Categories of test tools (management, static analysis, execution, performance, etc.)
- Benefits and risks of tool introduction
- Factors to consider when choosing a tool
- What a pilot project is and why it matters
One focused session is enough here. Do 10–15 practice questions.
Days 12–13: Full Mock Exams
Stop studying new material. Switch entirely to mock exams.
Day 12: Take a full 40-question timed mock exam (60 minutes). Review every question — including the ones you got right, to confirm your reasoning was solid.
Day 13: Take a second full mock exam. Focus your review on the chapters where you're still making errors. If you're below 75% on any chapter, go back and re-read those sections.
The real exam requires 65% to pass (26/40 correct). Aim to be consistently hitting 75–80% on practice before you sit it.
Day 14: Light Review + Rest
No cramming. Cramming the night before causes anxiety and doesn't stick.
What to do:
- Review your key notes from each chapter (30 minutes max)
- Skim through the 7 testing principles one more time
- Do 10 easy warm-up questions to build confidence
- Sleep well
The Most Common Failure Modes
Memorizing definitions without understanding them. The K2 questions — which are the majority — will catch you if you haven't understood why something works the way it does.
Skipping Chapter 4 exercises. The test design techniques (EP, BVA, decision tables) require practice to apply. Reading about them isn't enough.
Not timing yourself. The real exam is 60 minutes for 40 questions — 90 seconds per question. Practice at that pace.
Treating all chapters equally. Chapter 4 carries more weight than Chapter 6. Allocate your time accordingly.
Where to Practice
All 423 official ISTQB sample exam questions are available for free at istqbexam.com. The platform includes:
- Full exam simulation mode (40 questions, 60-minute timer, score report)
- Per-chapter filtering so you can drill weak areas
- AI explanations that explain the reasoning behind each answer, not just the correct option
No sign-up required. Open it, start practicing.
Two weeks is tight. But it's doable — if you're consistent, prioritize the right chapters, and practice with real questions. Good luck.