ISTQB CTFL-Foundation - ISTQB Certified Tester Foundation Level

Test implementation and execution involve several major tasks, which include:

i. Developing and prioritizing test cases, creating test data, writing test procedures, and optionally preparing the test harnesses and writing automated test scripts. This is crucial for ensuring that all aspects of the software are thoroughly tested and that the tests are prepared systematically.

ii. Creating the test suite from the test cases for efficient test execution. This helps organize the test cases in a way that optimizes the testing process and ensures coverage.

iii. Verifying that the test environment has been set up correctly. Ensuring that the test environment is correctly configured is critical for valid test results.

iv. Determining the exit criteria is part of the test planning phase, not the implementation and execution phase.

According to the ISTQB CTFL Syllabus, version 4.0, these activities are critical for the successful implementation and execution of tests. Therefore, the statement "i, ii, iii are true and iv is false" accurately reflects the tasks involved in this phase​​.

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.

Independent Verification & Validation (IV&V) is performed by an entity outside the project's sphere of influence to provide an unbiased assessment of the software product. This independence helps ensure that the verification and validation processes are objective and not influenced by the project's internal dynamics. Reference: ISTQB CTFL Syllabus V4.0, Section 1.4.1​​.

Structure-based (white-box) test case design techniques involve deriving test cases systematically from the delivered code. The ISTQB CTFL syllabus v4.0 describes that these techniques focus on the internal structure of the software, using knowledge of the code to create test cases that ensure comprehensive coverage of the code's pathways and logic​​.

Debugging is the process that developers follow to find, analyze, and fix the root causes of defects in the software. This includes identifying the source of the problem, correcting the code, and then testing the changes to ensure the defect has been properly fixed and that the fix does not introduce new issues.

Complete statement and branch coverage means that you have tested every statement and every branch in the program. Statement coverage ensures that every executable statement in the code is executed at least once, while branch coverage ensures that every possible path (true and false conditions) through the program's branches (such as IF statements) is executed. Achieving both covers a significant portion of the code, providing a thorough validation of its logic. Reference: ISTQB CTFL Syllabus V4.0, Section 4.3.2​​.

For reviewing safety-critical components in a software project, the most adequate review types are Inspections and Technical Reviews. Inspections are a formal review technique with a well-defined process that includes thorough preparation, examination, and documentation, making them suitable for critical components. Technical Reviews involve a detailed examination of the technical aspects of the software and are conducted by experts, which ensures that any potential issues are identified and addressed early.

A deviation from the specified or expected behavior that is visible to end-users is defined as a "failure." According to the ISTQB CTFL Syllabus, version 4.0:

Anerroris a human action that produces an incorrect result.

Afault(also known as a defect or bug) is a flaw in a component or system that can cause the system to fail to perform its required function.

Afailureoccurs when a fault is executed, leading to a deviation from the expected behavior, and this deviation becomes apparent to the end-users.

Thus, a visible deviation from the specified or expected behavior is termed a failure in the context of software testing​​.

The most valid goal for a test team is to cause as many failures as possible so that faults can be identified and corrected. This goal aligns with the primary objective of testing, which is to discover defects and ensure they are addressed before the software is released to end-users. By focusing on causing failures, the test team can identify weaknesses in the software and provide valuable feedback for improvements.

According to the ISTQB CTFL Syllabus, version 4.0, the ultimate aim of testing is to find and fix defects to enhance the quality and reliability of the software. Proving that all faults are identified or that no faults will cause failures are unrealistic and less effective goals because it is impossible to guarantee that all defects have been found. Therefore, the goal of causing failures to find and fix faults is the most valid and practical approach for a test team​​.