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
- Distinguish an error, a defect and a failure, and apply the seven testing principles to a project.
- Compare component, integration, system and acceptance testing by objective, test basis and typical defects.
- Apply a review technique to a work product and tell an inspection from a walkthrough.
- Derive test cases with equivalence partitioning, boundary value analysis, decision tables and state transitions.
- Schedule test execution by priority and dependencies, and write a clear defect report.
- Classify test tools by purpose and weigh the benefits and risks of test automation.
Explore related topics
CTFL_001 exam content
6 domains · 23 topics · 617 questions
Fundamentals of Testing
This chapter sets out what testing is for and why projects need it. It covers the seven testing principles, the test process with its activities and work products, and how the mindsets of testers and developers differ.
Skills tested
- Identify typical objectives of testing and tell testing apart from debugging.
- Distinguish an error from a defect and a failure, and a root cause from its effects.
- Apply the seven testing principles, such as the pesticide paradox, to a project situation.
- Describe each test activity and the work products it produces.
- Explain why traceability between the test basis and the test work products matters.
Official topics
- What is Testing
- Why is Testing Necessary
- Seven Testing Principles
- Test Process
- The Psychology of Testing
Testing Throughout the Software Development Lifecycle
This chapter places testing inside sequential and iterative development models. It compares the four test levels and the main test types, and it covers maintenance testing with impact analysis.
Skills tested
- Relate each development activity to its test activity in sequential and iterative models.
- Compare component, integration, system and acceptance testing by objective and responsibility.
- Compare functional, non-functional and white-box testing at any test level.
- Tell confirmation testing from regression testing after a change.
- Recognize triggers for maintenance testing and use impact analysis to scope it.
Official topics
- Software Development Lifecycle Models
- Test Levels
- Test Types
- Maintenance Testing
Static Testing
Static testing finds defects without running the code, for example by reviewing requirements, designs or code. This chapter covers the work product review process, the roles in a formal review, the four review types and what makes a review succeed.
Skills tested
- Name the work products that static testing can examine, from user stories to code.
- Explain how static and dynamic testing differ in their objectives and in the defects they find.
- Tell informal reviews, walkthroughs, technical reviews and inspections apart.
- Apply a checklist-based or role-based review technique to a work product.
Official topics
- Static Testing Basics
- Review Process
Test Techniques
This chapter has the most course time in the 2018 syllabus. Candidates derive test cases with black-box techniques, explain statement and decision coverage, and describe the experience-based techniques.
Skills tested
- Apply equivalence partitioning and boundary value analysis to derive test cases from requirements.
- Derive test cases from a decision table and from a state transition diagram.
- Explain how to derive test cases from a use case.
- Explain statement coverage, decision coverage and the value of each.
- Explain error guessing, exploratory testing and checklist-based testing.
Official topics
- Categories of Testing Techniques
- Black-box Test Techniques
- White-box Test Techniques
- Experience-based Test Techniques
Test Management
This chapter treats testing as work to plan, track and report. It covers independent testing, test plans and estimation, monitoring and control, configuration management, risk-based testing and defect management.
Skills tested
- Weigh the benefits and drawbacks of independent testing.
- Give examples of entry and exit criteria and of factors that affect test effort.
- Compare metrics-based and expert-based test estimation.
- Define risk level from likelihood and impact, and separate product risks from project risks.
- Write a defect report for a defect found during testing.
Official topics
- Test Organization
- Test Planning and Estimation
- Test Monitoring and Control
- Configuration Management
- Risks and Testing
- Defect Management
Tool Support for Testing
This chapter sorts test tools by purpose and by the test activities they support. It also covers the benefits and risks of test automation, how to select a tool, and why a pilot project comes before wide use.
Skills tested
- Classify test tools by the test activities they support.
- Identify the benefits and risks of test automation.
- Apply the main principles for selecting a tool, and recall what a pilot project is for.
- Name the success factors for bringing a tool into an organization.
Official topics
- Test Tool Considerations
- Effective use of Tools
Requirements
- No formal prerequisites: ISTQB asks only for an interest in software testing.
- Recommended: some background in development or testing, such as six months as a system or user acceptance tester or as a developer.
- Recommended: a course accredited by an ISTQB member board, although the exam does not require one.
About the CTFL_001 exam
CTFL_001 is the ISTQB Foundation Level exam built on the 2018 syllabus (version 3.1), for testers and anyone who works with them. Most of its learning objectives ask the candidate to recall or explain an idea. A smaller set asks for applied work: deriving test cases with four black-box techniques, applying a review technique, scheduling test execution and writing a defect report. CTFL v4.0 is the newer version of the exam, built on a rewritten syllabus. Passing earns the ISTQB Certified Tester Foundation Level certificate, which does not expire.
Test Techniques has the most course time in the 2018 syllabus. Its apply-level questions need careful, step-by-step work. The explanations in the PlanetCert practice test walk through how each technique reaches its answer, such as which values boundary value analysis picks at the edges of a range. Flashcard Mode suits the recall-level vocabulary of Fundamentals of Testing and Test Management. Brainy AI Assistant can turn a short requirement into a state transition table, or show how statement and decision coverage are measured for a few lines of code.
How to earn the certification
- Earns
- ISTQB Certified Tester Foundation LevelFoundation
The Foundation Level certificate does not expire.
- After
- CTAL-TA Advanced Level Test Analyst
An Advanced Level exam in the ISTQB Core stream, for testers who analyze and design tests.
- CTAL-TTA Advanced Level Technical Test Analyst
An Advanced Level exam in the Core stream, for testers who work closer to the code and the system's technical qualities.
- ctal-tm Advanced Level Test Management
An Advanced Level exam in the Core stream, for testers who plan, lead and report on testing.
- CTAL-TA Advanced Level Test Analyst
How to prepare for CTFL_001
- 1
Check the syllabus version first
This practice test follows the 2018 syllabus, and CTFL v4.0 is the newer version. Version 3.1 teaches decision coverage, for example, where the newer syllabus uses branch coverage. Confirm which version the exam provider offers before choosing study material.
- 2
Learn the terms chapter by chapter
ISTQB can examine every chapter at the recall level, so terms such as test basis, root cause and impact analysis must be exact. Drill them with the ISTQB glossary and Flashcard Mode.
- 3
Derive test cases on paper
Take one short requirement and derive tests with equivalence partitioning, boundary value analysis, a decision table and a state transition diagram. These are apply-level objectives in Test Techniques, the chapter with the most course time.
- 4
Rehearse a review and a defect report
Review a short requirements page with a checklist, then write a defect report for one finding, with its expected and actual results. Both tasks are apply-level objectives in the 2018 syllabus.
- 5
Close with timed practice runs
Take the CTFL_001 practice test in Timed Mode, then sort the missed questions by chapter. Ask Brainy AI Assistant to rework any technique question that went wrong, one step at a time.
Start a timed CTFL_001run
ISTQB recommends training from an Accredited Training Provider, in a classroom, virtual or e-learning course. Self-study with the syllabus and its recommended reading is also an option.
Who CTFL_001 is for
- Testers, test analysts and test engineers whose training followed the 2018 Foundation Level syllabus.
- Developers and user acceptance testers who want ISTQB's shared terms for defects, test levels and techniques.
- Project, quality and development managers who need a working view of how testing is planned and reported.
Typical job titles: Software tester · Test analyst · Test engineer · User acceptance tester · Software developer · Test manager
CTFL_001 glossary
17 terms from the exam objectives and the vendor's official material, each defined in a sentence.
- Absence-of-errors fallacy
- The mistaken belief that finding and fixing many defects is enough for a system to succeed. It can still fail to meet users' needs.
- Alpha and beta testing
- Acceptance testing by potential users or operators: alpha testing at the developer's site, beta testing at the users' own sites.
- Boundary Value Analysis
- A black-box technique that tests the values at the edges of each equivalence partition, where defects often occur.
- Confirmation bias
- The tendency to favor information that fits existing beliefs, which can make authors slow to accept defects in their own work.
- Confirmation testing (re-testing)
- Running the tests that failed again after a fix, to check that the defect is gone.
- Decision coverage
- The share of decision outcomes in the code, such as the true and false results of an if statement, that a set of tests has run.
- Decision Table Testing
- A black-box technique that lists combinations of conditions and the action the system should take for each combination.
- Defect density
- The number of defects found in a work product divided by its size, such as defects per thousand lines of code.
- Equivalence Partitioning
- A black-box technique that splits inputs or outputs into groups the system should treat the same way, then tests one value from each group.
- Error guessing
- An experience-based technique in which the tester predicts likely mistakes and designs tests to expose them.
- Exploratory testing
- Testing in which the tester designs, runs and evaluates tests at the same time, learning about the system along the way.
- Impact analysis
- Working out which parts of a system a change affects, to decide how much maintenance testing it needs.
- Independent testing
- Testing done by someone other than the author of the work, from a fellow developer to a separate test team.
- Pesticide paradox
- The principle that repeating the same tests stops finding new defects, so tests need regular review and change.
- State Transition Testing
- A black-box technique that checks how a system moves between states when events occur, including transitions that should not be allowed.
- Statement coverage
- The share of executable statements in the code that a set of tests has run.
- Test basis
- The source that tests are designed from, such as requirements, user stories or code.