Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
Which of the following are most likely to be used when developing a test strategy or test approach?
(i) Failure-based approach
(ii)Test specification approach
(iii) Model-based approach
(iv)Finance-based approach
Developing a test strategy or test approach often involves using a failure-based approach and a model-based approach. The failure-based approach focuses on anticipating potential failures and designing tests to expose these failures. The model-based approach uses models of the system's behavior or structure to design test cases systematically. These approaches help in creating a robust and comprehensive test strategy. Reference: ISTQB CTFL Syllabus V4.0, Section 5.2.2.
Which of the following comparisons of component testing and system testing are TRUE?
Component testing focuses on the individual parts of the software, often using design specifications, component specifications, or data models to derive test cases. In contrast, system testing evaluates the entire system's functionality and performance, using requirements and functional specifications or use cases to develop test cases. The ISTQB CTFL Syllabus clarifies these distinctions, emphasizing the different sources for test case derivation and the scopes of each testing level.
Which is not a major task of test implementation and execution?
Checking test logs against the exit criteria specified in test planning is not a major task of test implementation and execution. This activity is more related to evaluating exit criteria and reporting. Major tasks of test implementation and execution include developing and prioritizing test cases, creating test data, writing test procedures, optionally preparing test harnesses, and writing automated test scripts, logging the outcome of test execution, and verifying that the test environment has been set up correctly.
What factors should be considered to determine whether enough testing has been performed?
(i) The exit criteria.
(ii) The budget.
(iii) How big the test team is.
(iv) The product's risk profile.
(v) How good the testing tools are.
(vi) Sufficient details of the system status to allow decisions
Determining whether enough testing has been performed involves considering several factors. These include:
(i) The exit criteria, which define the conditions that must be met to conclude testing. (ii) The budget, which affects the extent of testing that can be conducted. (iv) The product's risk profile, which helps prioritize testing efforts on high-risk areas. (vi) Sufficient details of the system status to allow decisions, ensuring that stakeholders have the necessary information to make informed decisions about the software's readiness.
These factors together ensure a balanced and informed decision-making process regarding the sufficiency of testing.
Which statement BEST describes when test planning should be performed? [K1]
Test planning should be a continuous activity throughout the software development lifecycle. This ensures that the test plans remain relevant and effective, adapting to any changes in the project scope, requirements, or timelines.
How many test cases are necessary to cover all the possible sequences of statements (paths) for the following program fragment?
Assume that the two conditions are independent of each other : -if (Condition 1)then statement 1else statement 2if (Condition 2)then statement 3
To cover all possible sequences of statements (paths) in the given program fragment, considering two independent conditions, we have the following scenarios:
Condition 1 true, Condition 2 true
Condition 1 true, Condition 2 false
Condition 1 false, Condition 2 true
Condition 1 false, Condition 2 false
These scenarios require 4 test cases to ensure all paths are tested. Reference: ISTQB CTFL Syllabus V4.0, Section 4.3.3.
What benefits do static analysis tools have over test execution tools?
Exam domains verified against: Official ISTQB CTFL-Foundation exam guide, last checked October 2026.
This topic covers testing fundamentals, including principles, objectives, the necessity of testing, and the test process. It explores major activities, testware, and essential testing skills crucial for software testing professionals.
This topic covers how testing integrates into various development methodologies, including test-first and DevOps approaches. It also explores different test levels, test types, and maintenance testing.
Sample question from this domain above: Q2
This topic covers essential concepts of static testing, including the fundamentals of feedback and the review process. It emphasizes the importance of early defect detection and process improvement in software testing.
This topic covers applying black-box, white-box, and experience-based techniques to derive test cases from software work products. It also explores collaboration-based test approaches.
Sample question from this domain above: Q7
This topic covers managing test activities, including planning and estimating test efforts, understanding the impact of risks on testing scope, and monitoring and controlling test activities. It also focuses on utilizing configuration management for testing support and effectively reporting defects.
This topic covers test tools, focusing on classifying tools and understanding the risks and benefits of test automation. It includes identifying different types of testing tools, assessing their advantages, limitations, and impact on testing efficiency and effectiveness.
Sample question from this domain above: Q1
This foundational section of the exam is tailored for test managers, quality assurance professionals, and software testers. It delves into the core essence of testing, exploring its fundamental objectives and how they align with overall software quality goals. Candidates will gain a comprehensive understanding of what testing entails, including its scope, purpose, and critical role in the software development lifecycle. The section also draws a clear distinction between testing and debugging, two often conflated but distinct processe
Common questions about the exam itself
