200+ Free ISTQB Foundation Practice Questions

Pass your ISTQB Certified Tester Foundation Level (CTFL v4.0) exam on the first try — instant access, no signup required.

✓ No registration✓ No credit card✓ No hidden fees✓ Start practicing immediately

~85-90% Pass Rate

200+ Questions

100% Free

1 / 200

Question 1

Score: 0/0

What is the primary objective of software testing?

To prove that the software has no defects

To find defects and provide information about quality to stakeholders

To write test cases that cover all possible scenarios

To ensure the software meets all user requirements

to track

2026 Statistics

Key Facts: ISTQB Foundation Exam

85-90%

Est. Pass Rate

Industry estimate

26/40

Passing Score

65%

20-40 hrs

Study Time

Recommended

60 min

Exam Duration

75 min non-native

$229

Exam Fee

ASTQB/ISTQB

Lifetime

Cert Valid

No renewal needed

The ISTQB Foundation Level (CTFL v4.0) requires a 65% passing score (26 correct answers out of 40 multiple-choice questions). The exam takes 60 minutes (75 minutes for non-native English speakers). Chapter 4 (Test Techniques) and Chapter 5 (Test Management) carry the most weight at approximately 22% and 18% respectively. The certification is valid for life and serves as a prerequisite for all advanced ISTQB certifications.

Sample ISTQB Foundation Practice Questions

Try these sample questions to test your ISTQB Foundation exam readiness. Each question includes a detailed explanation. Start the interactive quiz above for the full 200+ question experience with AI tutoring.

1What is the primary objective of software testing?

A.To prove that the software has no defects

B.To find defects and provide information about quality to stakeholders

C.To write test cases that cover all possible scenarios

D.To ensure the software meets all user requirements

Explanation: The primary objective of testing is to find defects and provide information about the quality of the software to stakeholders. Testing cannot prove the absence of defects (exhaustive testing is impossible), and while it helps verify requirements, its main purpose is to identify issues and assess quality. Writing test cases is a means to an end, not the primary objective.

2Which of the following best describes the difference between testing and debugging?

A.Testing is performed by developers, debugging is performed by testers

B.Testing finds defects, debugging fixes defects

C.Testing is manual, debugging is automated

D.There is no difference between testing and debugging

Explanation: Testing is the process of finding defects, while debugging is the process of locating, analyzing, and fixing defects. Testing is performed by testers (and sometimes developers), while debugging is typically performed by developers. Both can involve manual and automated activities.

3What is the purpose of static testing compared to dynamic testing?

A.Static testing requires code execution, dynamic testing does not

B.Static testing examines work products without execution, dynamic testing requires execution

C.Static testing is performed by developers only, dynamic testing by testers only

D.Static testing finds runtime errors, dynamic testing finds syntax errors

Explanation: Static testing examines work products (code, requirements, design documents) without executing the software. Dynamic testing requires executing the software to observe its behavior. Both types of testing can be performed by various stakeholders, and static testing typically finds different types of defects than dynamic testing.

4Which of the following is NOT a typical quality attribute that testing can assess?

A.Functional correctness

B.Performance efficiency

C.Development team size

D.Security

Explanation: Development team size is a project management attribute, not a quality attribute of the software product. Testing typically assesses quality attributes such as functional correctness (does it work correctly?), performance efficiency (is it fast enough?), security (is it protected against attacks?), usability, reliability, and maintainability.

5A tester finds that a banking application allows negative amounts to be withdrawn. What type of defect is this?

A.Performance defect

B.Security defect

C.Functional defect

D.Usability defect

Explanation: This is a functional defect because the software is not performing its intended function correctly. The business logic should prevent negative withdrawals, but it fails to do so. A security defect would involve unauthorized access, a performance defect would involve slow response times, and a usability defect would involve difficulty in use.

6What is meant by "testware" in software testing?

A.Hardware used for testing

B.Work products produced during the test process

C.Software bugs found during testing

D.Tools used exclusively by test managers

Explanation: Testware refers to work products produced during the test process, including test plans, test cases, test scripts, test data, test logs, and defect reports. These artifacts are essential for planning, designing, executing, and evaluating tests.

7In the context of the seven testing principles, what does "absence-of-errors fallacy" mean?

A.Finding and fixing defects does not help if the system is unusable

B.Testing can prove that defects are absent

C.All software contains errors that cannot be found

D.Errors are only present during development, not in production

Explanation: The absence-of-errors fallacy states that finding and fixing defects does not help if the system built is unusable or does not fulfill users' needs and expectations. Even software with few defects can fail if it does not meet user requirements or is difficult to use.

8Why is "exhaustive testing is impossible" considered a fundamental testing principle?

A.Testers do not have enough time to test everything

B.It is theoretically possible but practically infeasible to test all combinations

C.Testing tools cannot handle large amounts of data

D.Developers do not provide complete specifications

Explanation: Exhaustive testing (testing all possible inputs, paths, and combinations) is theoretically possible for simple systems but practically infeasible for real-world software due to the vast number of possible combinations. This principle emphasizes the need for risk-based testing and prioritization to focus testing efforts where they will be most effective.

9According to the principle of "early testing", when should testing activities begin?

A.After code is written

B.During the requirements phase

C.After the first release

D.Only when defects are reported

Explanation: The principle of early testing states that testing activities should start as early as possible in the software development lifecycle, ideally during the requirements phase. Early testing helps find defects when they are cheaper to fix and prevents them from propagating to later stages.

10What does the "clustering defect" principle state?

A.Defects are evenly distributed throughout the code

B.A small number of modules contain most of the defects

C.Defects only occur in complex modules

D.Defects cluster in the user interface only

Explanation: The defect clustering principle (also known as the Pareto Principle in testing) states that a small number of modules typically contain most of the defects. This knowledge helps testers focus their testing efforts on high-risk areas where defects are more likely to be found.

About the ISTQB Foundation Exam

The ISTQB Certified Tester Foundation Level (CTFL v4.0) is the most widely recognized software testing certification globally. It provides essential knowledge and skills for software testing professionals, covering testing fundamentals, software development lifecycle testing, static testing, test techniques (black-box, white-box, experience-based), test management, and tool support.

Questions

40 scored questions

Time Limit

60 minutes (75 min non-native)

Passing Score

65% (26/40)

Exam Fee

$229 USD (ISTQB / ASTQB / National Boards)

ISTQB Foundation Exam Content Outline

17%

Fundamentals of Testing

Testing concepts, seven testing principles, test process (planning, analysis, design, implementation, execution, completion), and psychology of testing

18%

Testing Throughout the Software Development Lifecycle

Testing in sequential and iterative models, test levels (component, integration, system, acceptance), test types (functional, non-functional, black-box, white-box), and maintenance testing

13%

Static Testing

Static testing basics, benefits, work products that can be examined, static analysis tools, and review process (informal reviews, walkthroughs, technical reviews, inspections)

22%

Test Techniques

Black-box techniques (equivalence partitioning, boundary value analysis, decision tables, state transition, use case), white-box techniques (statement, decision coverage), and experience-based techniques (error guessing, exploratory testing)

18%

Test Management

Test organization, planning and estimation, risk management (product and project risks), monitoring and control, configuration management, and defect management

12%

Tool Support for Testing

Test tool considerations (management tools, static testing tools, test execution tools), benefits and risks, and test automation considerations

How to Pass the ISTQB Foundation Exam

What You Need to Know

Passing score: 65% (26/40)
Exam length: 40 questions
Time limit: 60 minutes (75 min non-native)
Exam fee: $229 USD

Keys to Passing

Complete 500+ practice questions
Score 80%+ consistently before scheduling
Focus on highest-weighted sections
Use our AI tutor for tough concepts

ISTQB Foundation Study Tips from Top Performers

1Focus on Chapter 4 (Test Techniques, 22%) — master equivalence partitioning, boundary value analysis, and decision tables

2Understand the seven testing principles deeply — expect 3-4 questions on these foundational concepts

3Study Chapter 2 (SDLC Testing, 18%) — know test levels, test types, and how testing fits in Agile vs Waterfall

4Practice calculating boundary values for ranges and understanding equivalence partitions

5Know the differences between white-box (structural) and black-box (specification-based) testing

6Understand risk-based testing — how product risks and project risks affect testing

7Learn the review types hierarchy: informal review, walkthrough, technical review, inspection

8Complete 200+ practice questions and score 80%+ consistently before scheduling the exam

Frequently Asked Questions

What is the ISTQB Foundation Level passing score?

The ISTQB Foundation Level exam requires a passing score of 65%, which equals 26 correct answers out of 40 multiple-choice questions. The exam duration is 60 minutes (75 minutes if the exam is taken in a non-native language). There is no negative marking, so candidates should answer all questions.

How hard is the ISTQB Foundation exam?

The ISTQB Foundation Level is considered an entry-level certification with an estimated pass rate of 85-90% for well-prepared candidates. Most candidates who study the syllabus and complete 200+ practice questions pass on their first attempt. The exam tests understanding of testing concepts rather than hands-on testing experience, making it accessible to newcomers while still valuable for experienced testers.

What are the six chapters of the ISTQB CTFL v4.0 syllabus?

The ISTQB CTFL v4.0 syllabus consists of: Chapter 1 - Fundamentals of Testing (~17%): concepts, principles, test process, psychology; Chapter 2 - Testing Throughout the SDLC (~18%): models, test levels, test types; Chapter 3 - Static Testing (~13%): reviews, static analysis; Chapter 4 - Test Techniques (~22%): black-box, white-box, experience-based; Chapter 5 - Test Management (~18%): organization, planning, risks, monitoring; Chapter 6 - Tool Support for Testing (~12%): tool types, automation.

How long should I study for ISTQB Foundation?

Most candidates need 20-40 hours of study time depending on background. With no testing experience: 30-40 hours. With some testing experience: 20-30 hours. Key study activities: 1) Read the official ISTQB CTFL v4.0 syllabus (2-3 times), 2) Understand the seven testing principles and when to apply them, 3) Practice test techniques (equivalence partitioning, boundary value analysis, decision tables), 4) Study test management concepts (estimation, risk, monitoring), 5) Complete 200+ practice questions and score 80%+ consistently.

Is ISTQB Foundation certification worth it in 2026?

Yes — ISTQB Foundation remains highly valuable: 1) It is the most widely recognized software testing certification globally with 1.1+ million certificates issued, 2) Many employers require or prefer ISTQB certification for QA and testing roles, 3) It provides a common vocabulary and framework for testing professionals, 4) It is a prerequisite for all advanced ISTQB certifications (Advanced Level, Specialist), 5) CTFL v4.0 includes modern topics like Agile testing, DevOps, and test automation considerations, 6) The certification is valid for life with no renewal required.

What is the difference between ISTQB CTFL v3.1 and v4.0?

CTFL v4.0 (released May 2023) represents a major update: 1) New topics include Agile/DevOps/Continuous Delivery integration, test automation strategy, collaborative user story writing, BDD (Behavior-Driven Development), and shift-left testing; 2) Updated terminology aligns with current industry practices; 3) Enhanced coverage of risk-based testing and test techniques; 4) v3.1 was retired in May 2024, so all new candidates take v4.0; 5) The exam format remains the same (40 questions, 65% passing score).

What test techniques are covered in the ISTQB Foundation exam?

The exam covers three categories: Black-box techniques: Equivalence partitioning, Boundary value analysis (2-value and 3-value), Decision table testing, State transition testing, Use case testing; White-box techniques: Statement coverage, Decision/branch coverage; Experience-based techniques: Error guessing, Exploratory testing, Checklist-based testing. Chapter 4 carries the most weight (~22%), so thorough understanding of these techniques is essential.