CTFL-Foundation ISTQB Certified Tester Foundation Level Free Practice Exam Questions (2025 Updated)

Regression testing is testing that nothing has regressed. Retesting (or confirmation testing) confirms the fix is correct by running the same test after the fix has been made. No other option has both of these as true.

The typical sequence of formal review activities includes planning, kick-off, individual preparation, and review meeting. The planning phase sets the scope and objectives, the kick-off initiates the review process, individual preparation involves participants reviewing the materials on their own, and then the review meeting is held to discuss the findings. Reference: ISTQB CTFL Syllabus V4.0, Section 3.2.2​​.

Non-functional requirements define how the system performs a certain function, rather than specific behaviors or functions of the system. Security, performance, usability, reliability, and maintainability are common examples of non-functional requirements. Ensuring the security of customer details is a non-functional requirement because it specifies a quality attribute that the system must have. Reference: ISTQB CTFL Syllabus V4.0, Section 4.1​​.

The cost of fixing a fault increases as the software progresses through the development lifecycle. Fixing defects identified early in the requirements or design phases is less expensive compared to fixing those found later in testing or after the software has been deployed. This is due to the larger impact on the system, more extensive rework required, and potential disruptions to the user experience in later stages.

Testing provides valuable information about the quality of the software by identifying defects and issues before the software is released. It helps stakeholders make informed decisions about the release and deployment of the software. While testing can identify defects and provide confidence in the quality of the software, it cannot guarantee the absence of defects or ensure that thesoftware quality will inherently increase. The primary goal of testing is to reveal problems and provide an indication of the software's current state of quality.

According to the ISTQB Glossary, regression testing is performed to ensure that changes or modifications in the software have not introduced new defects. The primary purpose of regression testing is to verify that the existing functionality of the software remains unaffected by recent changes, enhancements, or bug fixes.

The syllabus states that regression testing helps in confirming that the recent modifications do not negatively impact the previously working functionalities of the software​​.

Retesting, also known as confirmation testing, involves executing a previously failed test case after the defect has been fixed. The objective is to ensure that the original defect has been successfully removed. This type of testing is critical in verifying that the defect fixes are effective and that the software now operates as expected under the same conditions that previously caused the failure.

The odd one out among the given options is "Functional". The other options—White box, Glass box, and Structural—refer to testing techniques that involve examining the internal structure of the application. In contrast, functional testing focuses on testing the software against its functional requirements without considering its internal structures​​.

A failure is defined as the incorrect program behavior caused by a fault (defect) in the program. This means that when a defect is executed, it leads to the system not performing as expected, which is observed as a failure. This concept is clearly defined in the ISTQB CTFL Syllabus, where it distinguishes between defects (faults) and the resulting failures, emphasizing that failures are the manifestation of defects during the execution of the software​​.

The purpose of exit criteria is to determine when to stop testing. Exit criteria are specific conditions or set of conditions agreed upon to declare that a particular test level or a test activity is completed. These criteria are used to ensure that the testing process has reached a certain level of coverage and quality before it is considered complete. Typical exit criteria include achieving a certain level of code coverage, passing a specified number of tests, or fixing a certain number of defects. Reference: ISTQB CTFL Syllabus V4.0, Section 5.1.3 .

Iterative development involves users in the testing throughout the development process. This approach allows for continuous feedback from users, ensuring that the evolving system meets user requirements and expectations. Unlike the traditional waterfall model, iterative development accommodates changes and improvements based on user feedback, making it suitable for dynamic environments like website development. Reference: ISTQB CTFL Syllabus V4.0, Section 2.1.3​​.

The tasks of a tester typically include preparing and acquiring test data, implementing tests on all levels, executing and logging the tests, and creating test specifications. Interaction with the testtool vendor is generally not a primary task for testers but rather for test managers or tool specialists. The ISTQB CTFL Syllabus outlines these roles and responsibilities, emphasizing the technical tasks testers perform to ensure thorough testing and documentation​​.

The development strategy will affect the component testing (option (A)), in so far as it cannot be tested unless it has been built. Options (C) and (D) require the system to have been delivered; at these points the development strategy followed is not important to the tester. Option (B) needs knowledge of the development strategy in order to determine the order in which components will be integrated and tested.

Fault masking occurs when one defect prevents the detection of another defect. In other words, an error condition hides another error condition, making it more difficult to identify and correct all defects. This can happen in various scenarios, such as when a certain path of code execution is blocked by an existing error, preventing other potential errors from being executed and detected. Reference: ISTQB CTFL Syllabus V4.0, Section 1.5.5​​.

The moderator in a review is responsible for planning the review, running the review meeting, and ensuring that follow-up activities are completed. This role is crucial for the effectiveness of the review process, as highlighted in the ISTQB CTFL syllabus v4.0, which details the responsibilities and importance of the moderator in facilitating a productive and structured review​​.

When a defect is detected and fixed, the software should be retested to confirm that the original defect has been successfully removed. This process is called confirmation testing (or re-testing). According to the ISTQB CTFL Syllabus, version 4.0, confirmation testing involves re-running a test to verify that a specific defect has been fixed. The main objective of this type of testing is to ensure that the initial defect no longer exists after the fix has been applied.

The syllabus states that confirmation testing is distinct from regression testing, which checks for unintended side effects of changes in the software. Confirmation testing specifically targets the areas where defects were found and fixed to ensure those defects are resolved​​.

Exploratory testing is used when it is unclear what the system is supposed to do. Therefore test execution tools are of little use because expected results cannot be predicted.

However, the record feature of a test execution tool can be used to log the actions performed so that defects can be recreated (option (A)) and rectified more easily.

In the MASPAR case study, several key issues were highlighted. Security failures were attributed to untested parts of code (A), despite achieving complete statement and branch coverage, a serious bug was still missed in the MASPAR operating system (B). Additionally, an obscure error required testing the function with nearly every input value to find the two special-case failures (C). Therefore, all thesepoints together (D) illustrate the complexity and challenges in software testing. Reference: ISTQB CTFL Syllabus V4.0​​.