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 ISQI
Exam Format
Registration
Validity
Skills this practice test covers
- Apply the seven testing principles and tell testing apart from debugging.
- Explain how the chosen development lifecycle shapes testing, and tell test levels from test types.
- Run a review and choose the review type that fits a work product.
- Derive test cases with equivalence partitioning, boundary value analysis and decision tables.
- Measure statement coverage and branch coverage for a set of tests.
- Plan testing with entry and exit criteria, risk analysis and test effort estimates.
Explore related topics
CTFL exam content
6 domains · 50 topics · 255 of 262 questions sorted by domain
Fundamentals of Testing20%46 questions
This chapter sets out what testing is for and why it is needed. It links errors, defects, failures and root causes, and it states the seven testing principles. It also covers test activities, testware, test roles and the whole team approach.
Skills tested
- Tell testing apart from debugging and name typical test objectives.
- Trace how a human error leads to a defect, a failure and its root cause.
- Apply the seven testing principles, for example that exhaustive testing is impossible.
- Match test activities and tasks to the test management role and the testing role.
Questions by topic
- Testing Principles16
- Test Activities, Testware and Test Roles12
- Independence of Testing6
- Whole Team Approach5
- Errors, Defects, Failures, and Root Causes3
- Testing and Debugging3
- Retrospectives and Process Improvement1
Testing Throughout the Software Development Lifecycle15%44 questions
Testing changes with the development model. Candidates explain how the chosen software development lifecycle (SDLC) affects testing and separate test levels from test types. They also tell confirmation testing from regression testing and describe the triggers for maintenance testing.
Skills tested
- Explain how sequential, iterative and incremental models change when testing happens.
- Distinguish component, integration, system and acceptance testing.
- Separate confirmation testing from regression testing after a fix.
- Explain the shift-left approach and the role of testing in DevOps.
- Name triggers for maintenance testing, such as modifications and migration.
Questions by topic
- Shift Left4
- Test Types5
- Confirmation Testing and Regression Testing7
- Test Levels11
- DevOps and Testing4
- Maintenance Testing5
- Testing in the Context of a Software Development Lifecycle3
- Testing as a Driver for Software Development3
- Retrospectives and Process Improvement1
- Test Levels and Test Types1
Static Testing10%25 questions
Static testing finds defects without running the code. This chapter covers which work products can be reviewed, the value of early and frequent feedback, the review process and its roles, and the main review types.
Skills tested
- Pick the work products that static testing can examine, such as requirements or code.
- Compare static testing with dynamic testing.
- Run a review through its activities, with the author, moderator and reviewers in their roles.
- Choose between an informal review, a walkthrough, a technical review and an inspection.
Questions by topic
- Review Types5
- Static Testing Basics5
- Feedback and Review Process6
- Success Factors for Reviews3
- Value of Static Testing4
- Differences between Static Testing and Dynamic Testing2
Test Analysis and Design27.5%58 questions
This chapter carries the most exam questions and teaches the test techniques. Candidates apply black-box techniques, explain statement and branch coverage, and use experience-based techniques. They also work with collaboration-based approaches such as acceptance test-driven development (ATDD).
Skills tested
- Derive test cases with equivalence partitioning and boundary value analysis.
- Build a decision table and a state transition model from a requirement.
- Measure statement coverage and branch coverage for a set of tests.
- Use error guessing, exploratory testing and checklist-based testing.
- Write acceptance criteria in the Given-When-Then format and derive ATDD test cases.
Questions by topic
- Experience-based Test Techniques8
- Boundary Value Analysis6
- The Value of White-box Testing4
- Acceptance Test-driven Development (ATDD)5
- Collaboration-based Test Approaches5
- Decision Table Testing5
- Equivalence Partitioning5
- Branch Testing and Branch Coverage5
- State Transition Testing4
- Statement Testing and Statement Coverage3
- Test Techniques Overview5
- Exploratory Testing1
- Black-Box Test Techniques2
Managing the Test Activities22.5%69 questions
This chapter covers how testing is planned and controlled. It runs from test plans, entry and exit criteria and estimation to risk management. It ends with test monitoring and control, configuration management and defect reports.
Skills tested
- Write the parts of a test plan and set entry and exit criteria.
- Estimate test effort with planning poker or metrics-based estimation.
- Rate product risks by likelihood and impact, and let them guide testing.
- Prioritize test cases and apply the test pyramid.
- Write a defect report that a developer can act on.
Questions by topic
- Test Control4
- Defect Management9
- Risk Management11
- Entry Criteria and Exit Criteria5
- Test Effort Estimation7
- Test Monitoring, Test Control and Test Completion7
- Test Planning5
- Configuration Management7
- Communicating the Status of Testing4
- Test Case Prioritization3
- Test Pyramid4
- Test Completion3
Test Tools5%13 questions
The smallest chapter looks at how tools support testing. Candidates explain the main tool categories and weigh the benefits of test automation against its risks.
Skills tested
- Match tool categories, such as test management or performance testing tools, to testing tasks.
- Weigh automation benefits, such as faster execution, against risks, such as false confidence.
Questions by topic
- Benefits and Risks of Test Automation10
- Tool Support for Testing3
Requirements
- No formal prerequisites: anyone can book the exam.
- Recommended: at least six months of hands-on software testing.
- Recommended: a basic understanding of how software is developed.
About the CTFL exam
CTFL is the Foundation Level exam of the International Software Testing Qualifications Board (ISTQB), for anyone who tests software or works with testers. It checks how testing is planned, designed and carried out under the version 4.0 syllabus. Its six chapters run from testing principles and the development lifecycle to reviews, test techniques, test management and tools. Each learning objective has a knowledge level: K1 to remember, K2 to understand and K3 to apply. Passing earns the ISTQB Certified Tester Foundation Level certificate, which does not expire.
Managing the Test Activities has the most questions in the PlanetCert practice test, followed by Test Analysis and Design. The explanations work each technique step by step, for example which values two-value boundary testing picks for a range, or which branches a set of tests covers. Study Mode suits the K3 technique questions, because each explanation points to the step that went wrong, such as a missed partition. Brainy AI Assistant can build a decision table from a short requirement or explain how confirmation testing differs from regression testing.
How to earn the certification
- Earns
- ISTQB Certified Tester Foundation Level (CTFL)Foundation
ISTQB issues the Foundation Level certificate for life.
How to prepare for CTFL
- 1
Study the syllabus with the glossary
ISTQB publishes the v4.0 syllabus and the ISTQB Glossary for free. Learn each keyword the syllabus lists with the glossary's definition, since the exam uses those terms.
- 2
Work every technique on paper
Test Analysis and Design carries the most exam questions, and many ask the candidate to apply a technique. Practise partitions and boundaries for an age field, a decision table for a discount rule and a state diagram for a login.
- 3
Give each principle a project example
Write one real example for each testing principle, such as defects cluster together or the absence-of-errors fallacy. Scenario questions on the principles then become easier to place.
- 4
Write a risk list and a defect report
Managing the Test Activities has the most questions in this practice test. Rate a few product risks by likelihood and impact, then write one full defect report with expected and actual results.
- 5
Finish with the official sample exams
Take the CTFL practice test in Timed Mode, then try ISTQB's official sample exams. Ask Brainy AI Assistant to rework any boundary or coverage question that went wrong.
Start a timed CTFLrun
ISTQB accredited training providers teach the CTFL v4.0 syllabus in classroom, virtual and e-learning courses. Self-study with the syllabus and its recommended reading is also an option.
Who CTFL is for
- Software testers, test analysts and test engineers who want the ISTQB terms and techniques behind their work.
- Developers and business analysts who design or review tests as part of a team.
- Test, quality and project managers who plan testing or report on it.
- User acceptance testers who check software against business needs.
Typical job titles: Software tester · Test analyst · QA engineer · Test engineer · Test manager
CTFL glossary
18 terms from the exam objectives and the vendor's official material, each defined in a sentence.
- 2-value boundary testing
- A form of boundary value analysis that tests each boundary value and its closest neighbor in the next partition.
- Absence-of-errors fallacy
- The testing principle that finding and fixing many defects does not ensure the system meets users' needs.
- Acceptance Test-Driven Development (ATDD)
- A collaborative approach in which the team writes acceptance tests from the acceptance criteria before the feature is built.
- Boundary Value Analysis
- Testing the values at the edges of ordered partitions, where defects often appear.
- Branch coverage
- The share of branches in the code, such as both outcomes of a decision, that a set of tests has exercised.
- Confirmation testing (retesting)
- Running tests again after a fix to check that the defect is gone.
- Decision Table Testing
- A technique that lists combinations of conditions with the actions each should cause, then tests each combination.
- Defects cluster together
- The testing principle that a small number of components usually contain most of the defects.
- Entry and exit criteria
- Conditions that must hold before a test activity starts (entry) and before it can be called complete (exit).
- Equivalence Partitioning
- Dividing inputs or outputs into partitions that the software should treat the same way, then testing one value from each.
- Exploratory Testing
- Testing in which the tester designs and runs tests at the same time, learning about the software along the way.
- Given-When-Then format
- A way to write acceptance criteria as a starting situation, an action, and the expected result.
- Planning poker
- A consensus-based estimation technique in which team members estimate effort with numbered cards and discuss the differences.
- Regression testing
- Testing that checks a change has not broken parts of the software that worked before.
- State Transition Testing
- Testing how a system moves between states in response to events, using a state diagram or a state table.
- Statement coverage
- The share of executable statements in the code that a set of tests has run.
- Testware
- The work products created during testing, such as test plans, test cases, test data and test reports.
- Whole Team Approach
- The practice in which every team member, not only testers, shares responsibility for quality.