CTFL_SYLL_4.0 Exam Preparation Material | ISTQB Certified Tester Foundation Level (CTFL)

Explanation:
Risk register is a test planning work product as it documents identified risks and their mitigation strategies.
Risk information falls under test monitoring and control work products as it involves ongoing evaluation and reporting of risks.
Test cases are part of test design work products as they are derived from test conditions and designed to execute the testing scenarios.
Test conditions belong to test analysis work products as they define the items or events of a system that are to be tested.

Explanation:
The testing of software does not demonstrate the absence of defects, but rather the presence of defects or the conformance of the software to the specified requirements1. Testing can never prove that the software is defect-free, as it is impossible to test all possible scenarios, inputs, outputs, and behaviors of the software2. Testing can only provide a level of confidence in the quality of the software, based on the coverage, effectiveness, and efficiency of the testing activities3.
The other options are correct because:
A. Properly designed tests that pass reduce the level of risk in a system, as they verify that the system meets the expected quality attributes and satisfies the needs and expectations of the users and clients4. Risk is the potential for loss or harm due to the occurrence of an undesirable event5. Testing can help to identify, analyze, prioritize, and mitigate the risks associated with the software product and project6.
C. Software testing identifies defects, which can be used to improve development activities, as they provide feedback on the quality of the software and the effectiveness of the development processes7. Defects are flaws or errors in the software that cause it to deviate from the expected or required results or behavior. Testing can help to detect, report, track, and resolve the defects, and prevent them from recurring in the future.
D. Performing a review of the requirement specifications before implementing the system can enhance quality, as it can ensure that the requirements are clear, complete, consistent, testable, and aligned with the needs and expectations of the users and clients. Requirements are the specifications of what the software should do and how it should do it. Testing can help to validate that the requirements are met by the software, and verify that the software is implemented according to the requirements.
Reference =
1 ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 10
2 ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 11
3 ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 12
4 ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 13
5 ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 97
6 ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 98
7 ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 14
[8] ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 15
[9] ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 16
[10] ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 17
[11] ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 18
[12] ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 19

Explanation:
A defect report should contain relevant details to help developers reproduce and fix the defect efficiently. The essential elements include:
Test object & environment (A)C To ensure reproducibility.
Title & summary (B)C For quick identification.
Expected vs. actual results (D)C To describe the discrepancy.
The structure of the test team (C)is irrelevant for defect tracking and resolution.
Reference: ISTQB CTFL v4.0 Syllabus, Section 5.5 C Defect Management

Explanation:
Branch coverage is a type of structural coverage metric that measures the percentage of branches or decision outcomes that are executed by the test cases. A branch is a point in the code where the control flow can take two or more alternative paths based on a condition.
For example, an if-else statement is a branch that can execute either the if-block or the else-block depending on the evaluation of the condition. Branch coverage ensures that each branch is taken at least once by the test cases, and thus reveals the behavior of the software under different scenarios. Branch coverage is also known as decision coverage or all-edges coverage.
Branch coverage is suitable for testing the cases where a specific action is not allowed, because it can verify that the test cases cover all the possible outcomes of the conditions that determine the action.
For example, if the program has a condition that checks if the manufacturing stage can be stopped, then branch coverage can ensure that the test cases cover both the cases where the stage can be stopped and where it cannot be stopped. This way, branch coverage can help identify any missing or incorrect branches that may lead to undesired or unsafe actions.
The other options are not correct because they are not suitable for testing the cases where a specific action is not allowed. Code coverage is a general term that encompasses various types of coverage metrics, such as statement coverage, branch coverage, data flow coverage, etc. Code coverage does not specify which type of coverage metric is used for the analysis. Data flow coverage is a type of structural coverage metric that measures the percentage of data flow paths that are executed by the test cases. A data flow path is a sequence of statements that define, use, or kill a variable. Data flow coverage is useful for testing the correctness and completeness of the data manipulation in the software, but not for testing the conditions that determine the actions. Statement coverage is a type of structural coverage metric that measures the percentage of statements or lines of code that are executed by the test cases. Statement coverage ensures that each statement is executed at least once by the test cases, but it does not reveal the behavior of the software under different scenarios. Statement coverage is a weaker criterion than branch coverage, because it does not account for the branches or decision outcomes in the code. Reference = ISTQB Certified Tester Foundation Level (CTFL) v4.0 syllabus, Chapter 4: Test Techniques, Section 4.3: Structural Testing Techniques, Pages 51-54.

Explanation:
Quality Assurance (QA) and Quality Control (QC) are both essential aspects of a comprehensive quality management system but they serve different purposes:
Quality Assurance (QA): QA is a process-oriented approach that focuses on preventing defects by improving the processes used to develop and test products. It involves setting up processes, methodologies, and standards to ensure that the product meets quality requirements.
Quality Control (QC): QC is a product-oriented approach that focuses on identifying defects in the final products. It involves activities such as inspection, testing, and review to ensure that the product meets the specified requirements and standards.
Thus, the main difference is that QA is process-oriented and preventive, while QC is product-oriented and corrective.