Why Study with PlanetCert?
The Latest Questions
Practice questions and exam topics aligned with the current exam objectives.
Detailed Explanations
Go beyond the answer. Master the material with comprehensive learning and professional explanations for every concept.

AI-Powered Insights
Personalized preparation guidance that adapts to your performance and identifies weak spots automatically.
Exam Information
Official specifications published by ISTQB
Exam Format
Registration
Validity
Skills this practice test covers
- Explain the seven testing principles and how testing differs from debugging.
- Place test levels, test types and shift-left practice in sequential, iterative and DevOps lifecycles.
- Run a review and pick the review type that fits a work product.
- Derive test cases with equivalence partitioning, boundary value analysis, decision tables and state transitions.
- Plan testing with entry and exit criteria, effort estimates and product risk analysis.
- Report defects and test status, and weigh the benefits and risks of test automation.
Explore related topics
CTFL-V4-0 exam content
6 domains · 54 topics · 238 of 617 questions are written for CTFL-V4-0
Fundamentals of Testing20%44 questions
This chapter sets out what testing is and why it is needed. Candidates separate testing from debugging, and errors from defects and failures, apply the seven principles, and describe test activities, testware, roles and the whole team approach.
Skills tested
- Tell testing from debugging, and an error from a defect and a failure.
- Apply the seven testing principles, such as early testing saves time and money.
- Match each test activity, from planning to completion, with the testware it produces.
- Weigh the benefits and drawbacks of independent testing.
Questions by topic
- 1.5.3 Independence of Testing4
- 1.4.1 Test Activities and Tasks9
- 1.2.3 Errors, Defects, Failures, and Root Causes5
- Testing Principles16
- 1.1.2 Testing and Debugging5
- 1.5.2 Whole Team Approach4
- 1.4.5 Roles in Testing1
Testing Throughout the Software Development Lifecycle15%38 questions
This chapter places testing inside sequential, iterative and DevOps lifecycles. Candidates distinguish test levels from test types, and confirmation testing from regression testing, and explain what triggers maintenance testing.
Skills tested
- Explain how the chosen lifecycle changes when and how testing happens.
- Describe test-first approaches such as ATDD and BDD, and the shift-left approach.
- Distinguish component, integration, system and acceptance testing.
- Use impact analysis to scope maintenance testing after a change.
Questions by topic
- 2.1.6 Retrospectives and Process Improvement3
- 2.1.4 DevOps and Testing4
- Maintenance Testing4
- 2.2.1 Test Levels7
- 2.2.3 Confirmation Testing and Regression Testing7
- 2.1.1 Impact of the Software Development Lifecycle on Testing4
- 2.2.2 Test Types5
- 2.1.5 Shift Left3
- 2.1.3 Testing as a Driver for Software Development1
Static Testing10%22 questions
Static testing finds defects without running the code. Candidates name the work products it can examine, explain the value of early and frequent feedback, and describe the review process, its roles and its types.
Skills tested
- List the work products that static testing can examine, from requirements to code.
- Explain why defects found early in reviews cost less to fix.
- Assign review roles such as author, facilitator, scribe and reviewer.
- Compare informal reviews, walkthroughs, technical reviews and inspections.
Questions by topic
- 3.1.3 Differences between Static Testing and Dynamic Testing3
- 3.2.3 Roles and Responsibilities in Reviews4
- 3.2.4 Review Types4
- 3.2.5 Success Factors for Reviews3
- 3.1.2 Value of Static Testing6
- 3.2.2 Review Process Activities2
Test Analysis and Design27.5%64 questions
The largest chapter on the exam teaches test techniques. Candidates derive test cases with black-box techniques, measure white-box coverage, apply experience-based techniques, and write user stories and acceptance criteria with the team.
Skills tested
- Derive test cases with equivalence partitioning and 2-value or 3-value boundary value analysis.
- Build decision tables and state transition diagrams, and check the coverage they reach.
- Calculate statement coverage and branch coverage for a piece of code.
- Apply error guessing, exploratory testing and checklist-based testing.
- Write acceptance criteria in the Given-When-Then format for ATDD.
Questions by topic
- 4.4.3 Checklist-Based Testing4
- 4.2.3 Decision Table Testing9
- 4.2.2 Boundary Value Analysis6
- 4.2.4 State Transition Testing9
- 4.3.2 Branch Testing and Branch Coverage4
- 4.5.1 Collaborative User Story Writing3
- 4.3.3 The Value of White-box Testing5
- 4.3.1 Statement Testing and Statement Coverage3
- 4.2.1 Equivalence Partitioning4
- 4.5.3 Acceptance Test-driven Development (ATDD)4
- 4.4.1 Error Guessing4
- 4.4.2 Exploratory Testing4
- Test Techniques Overview3
- 4.5.2 Acceptance Criteria2
Managing the Test Activities22.5%60 questions
This chapter covers planning and control. Candidates write test plans with entry and exit criteria, estimate effort, prioritize tests, analyze product risks, monitor progress, report status, and manage defects and configuration.
Skills tested
- Describe a test plan's content and the tester's part in iteration and release planning.
- Estimate test effort with techniques such as three-point estimation and planning poker.
- Rate a risk level from risk likelihood and risk impact.
- Plan test types with the test pyramid and the testing quadrants.
- Write a defect report that gives developers what they need.
Questions by topic
- 5.2.3 Product Risk Analysis5
- 5.1.6 Test Pyramid5
- 5.5.1 Defect Management6
- 5.2.4 Product Risk Control4
- 5.1.1 Purpose and Content of a Test Plan5
- 5.2.2 Project Risks and Product Risks4
- Configuration Management4
- 5.1.4 Estimation Techniques4
- 5.3.1 Metrics used in Testing3
- 5.3.2 Purpose, Content and Audience for Test Reports4
- 5.1.5 Test Case Prioritization3
- 5.1.7 Testing Quadrants2
- 5.1.2 Tester's Contribution to Iteration and Release Planning3
- 5.1.3 Entry Criteria and Exit Criteria3
- 5.3.3 Communicating the Status of Testing2
- Test Monitoring, Test Control and Test Completion3
Test Tools5%10 questions
The smallest chapter covers tool support. Candidates explain how different kinds of tools support testing, and weigh the benefits and risks of test automation.
Skills tested
- Match tool types, such as management, execution and DevOps tools, to the tasks they support.
- Weigh the benefits of test automation against its risks.
Questions by topic
- Benefits and Risks of Test Automation6
- Tool Support for Testing4
Requirements
- No formal prerequisites: anyone can book the exam.
- Recommended: a basic understanding of how software is developed, and some time on a software project.
- Recommended: a full read of ISTQB's CTFL v4.0 syllabus and its sample exams.
About the CTFL-V4-0 exam
CTFL-V4-0 is the version 4.0 exam for ISTQB's Certified Tester Foundation Level. ISTQB writes it for testers, and also for the developers, analysts and managers who work with them. It checks the basics that later ISTQB certificates build on: the testing principles, testing across the lifecycle, reviews, test techniques, test management and tools. Passing earns the ISTQB Certified Tester Foundation Level certificate, which does not expire.
Test Analysis and Design and Managing the Test Activities draw the most questions in the PlanetCert practice test, and the testing principles are its largest single topic. The explanations work through each technique step by step, for example where the boundary values of a partition lie. Flashcard Mode suits the ISTQB glossary terms, where one word, such as error, defect or failure, changes the answer. Brainy AI Assistant can check a decision table or a state transition diagram drawn for a practice question.
How to earn the certification
- Earns
- ISTQB Certified Tester Foundation Level (CTFL)Foundation
The CTFL certificate does not expire.
- After
- CTAL-TA Advanced Level Test Analyst
The Advanced Level exam for test analysts who design tests from the business side.
- ctal-tm Advanced Level Test Management
The Advanced Level exam for those who plan, run and lead testing.
- CTAL-TTA Advanced Level Technical Test Analyst
The Advanced Level exam for technical testing, such as white-box techniques and quality characteristics like security and performance.
- CTAL-TAE Advanced Level Test Automation Engineering
The Advanced Level exam for designing, building and maintaining test automation.
- CTAL-TA Advanced Level Test Analyst
How to prepare for CTFL-V4-0
- 1
Read the syllabus with the glossary
Work through the CTFL v4.0 syllabus chapter by chapter, and look up each keyword in the ISTQB glossary. Many answers turn on one exact term.
- 2
Practise each technique by hand
Draw partitions, boundary values, decision tables and state diagrams for a small form or a vending machine. Then count the coverage each set of tests reaches.
- 3
Hold a short review
Review a one-page requirement with a colleague, taking the author, facilitator and reviewer roles in turn, and log each defect found.
- 4
Plan the tests for one sprint
Write a short test plan with entry and exit criteria, an effort estimate and a list of product risks. This covers much of Managing the Test Activities.
- 5
Time the practice test, then the samples
Take the CTFL-V4-0 practice test in Timed Mode, then ISTQB's official sample exams. Ask Brainy AI Assistant why each wrong option is wrong.
Start a timed CTFL-V4-0run
ISTQB publishes the syllabus and the official sample exams, and courses come from training providers listed in ISTQB's directory.
Who CTFL-V4-0 is for
- New software testers who want a recognized first certificate.
- Developers and business analysts who work closely with testers.
- Project and quality managers who need the same testing terms as their teams.
- User acceptance testers who want a structured way to design tests.
Typical job titles: Software tester · Test analyst · Test engineer · QA engineer · Test manager · User acceptance tester
CTFL-V4-0 glossary
18 terms from the exam objectives and the vendor's official material, each defined in a sentence.
- Absence-of-defects fallacy
- The principle that removing many defects does not make a system succeed if it does not meet its users' needs.
- Acceptance Test-Driven Development (ATDD)
- A test-first approach in which the team writes acceptance tests from the acceptance criteria before the feature is built.
- Boundary value analysis
- A black-box technique that tests the values at the edges of ordered partitions, where defects are common.
- Branch coverage
- The proportion of branches in the code, such as both outcomes of a decision, that the tests have exercised.
- Confirmation testing
- Testing that checks whether a reported defect has really been fixed.
- Equivalence partitioning
- A black-box technique that divides data into partitions the system should treat the same way, and tests at least one value from each.
- Exit criteria
- Conditions that must be met before a test activity counts as finished, such as a coverage level being reached.
- Exploratory testing
- Testing in which the tester designs, runs and evaluates tests at the same time, learning about the system along the way.
- Regression testing
- Testing that checks whether a change has broken something that worked before.
- Root cause
- The underlying reason a defect occurred, such as a misunderstood requirement. Fixing it can prevent similar defects.
- Shift-left approach
- Starting testing activities earlier in the lifecycle, for example reviewing requirements before any code is written.
- State transition testing
- A black-box technique that tests how a system moves between states in response to events.
- Statement coverage
- The proportion of executable statements in the code that the tests have run.
- Test basis
- The material that tests are built from, such as requirements, user stories or design documents.
- Test pyramid
- A model with many fast, low-level tests at the base and fewer slow, high-level tests at the top.
- Testing quadrants
- A model that groups test types by whether they face the business or the technology, and whether they support the team or critique the product.
- Testware
- The work products made during testing, such as test plans, test cases, test data and test reports.
- Whole team approach
- An agile practice in which everyone on the team, not only the testers, shares responsibility for quality.