ISTQB CTFL-Foundation - ISTQB Certified Tester Foundation Level

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 usecases 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​​.

Reviewing the test basis is a key activity in the Test Analysis and Design phase. This phase involves analyzing the test basis documents (such as requirements, design specifications, and use cases) to identify test conditions and design test cases. The ISTQB CTFL Syllabus explains that thorough review of the test basis ensures that the tests are aligned with the specified requirements and design, improving the accuracy and relevance of the tests​​.

Debugging defects is not a testing objective. According to the ISTQB CTFL syllabus v4.0, the primary objectives of testing include finding defects, gaining confidence about the level of quality, providing information, and preventing defects. Debugging is a developer's activity that involves identifying the cause of defects and fixing them, which is different from the objectives of testing​​.

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​​.

The responsibility of conducting a test readiness review typically falls to the Test Manager. The Test Manager ensures that all necessary preparations for testing have been completed and that the testing environment, resources, and schedule are ready for the test execution phase. This role involves coordinating with different stakeholders to confirm that the testing process can proceed smoothly​​.

Answer (i) looks temptingly right, and the availability of tools might make the use of a technique more or less attractive, but it would not be decisive in the way that regulatory standards and tester knowledge are.

Answer (iii) is irrelevant because testing should be independent of development anyway, but it could tempt someone who is unsure about the relationship between development and testing.

Answer (v) is a factor in managing the test team, and experience would need to be maintained, but this should not influence the selection of techniques for a live project.

Designing the tests is part of the Test Analysis and Design phase, not the Test Implementation and Execution phase. The Test Implementation and Execution phase involves creating test suites, executing test cases, and comparing actual results with expected outcomes to identify any discrepancies​​.

Structural testing, also known as white-box testing, focuses on the internal structure of the software. It includes testing all paths, achieving decision coverage, and ensuring that all branches within the component calls are tested. Ensuring that users can navigate to all fields on the screen, however, is a form of functional testing, which focuses on the behavior and usability of the application from the user's perspective, rather than its internal structure​​.

During the test planning stage, it is important to assign resources for the planned activities. This ensures that the necessary personnel, equipment, and time are allocated to execute the test plan effectively. Analyzing the test basis, designing test environments, and writing a test execution schedule are activities that come after the initial planning and resource allocation​​.

The pesticide paradox in testing refers to the phenomenon where continuously using the same set of tests on the software eventually becomes less effective at finding new defects. Just as insects can develop resistance to pesticides over time, software defects become less detectable by tests that are not updated. Therefore, to maintain the effectiveness of testing, it is essential to regularly review and revise the test cases to introduce new tests and update existing ones​​.