ISTQB CTFL-2018 Practice Test - Questions Answers, Page 31

According to the syllabus, a test summary report is a document that summarizes the results and activities of a completed test level. It typically includes information such as test objectives, test items, test environment, test cases executed, defects found, incidents raised, and lessons learned. The answer C is incorrect because it would not typically be covered in a test summary report. The economic benefit of continuing testing beyond the planned date is not a relevant information for a completed test level, as it is more related to project management decisions. The other answers are correct because they are examples of information that would typically be covered in a test summary report.

According to the syllabus, configuration management is a process that establishes and maintains the consistency of a product's attributes throughout its life cycle. It involves identifying, controlling, tracking, and auditing changes to the product's components and documentation. Configuration management supports the test process by enabling the tester to reproduce the tested item through unique identification and version control. This ensures that the tester knows exactly what has been tested and can trace any defects or incidents to the correct version of the software under test. The answer A is correct because it best describes how configuration management supports the test process. The other answers are incorrect because they describe other aspects of testing that are not directly related to configuration management.

According to the syllabus, product risks are risks that affect the quality of the software product, such as defects, failures, or non-compliance with requirements or standards. Product risks can be identified and analyzed during the test planning phase, and mitigated by appropriate test design and execution. The answer C is correct because it lists three product risks: failure prone software delivered, software does not perform its intended functions, and poor data integrity and quality. The other answers are incorrect because they include project risks, which are risks that affect the management and control of the testing process, such as insufficient staff, test environment issues, or schedule delays.

According to the syllabus, a defect report is a document that records the occurrence, nature, and status of a defect. A defect report typically includes several fields that provide relevant information about the defect, such as its title, description, priority, status, environment, steps to reproduce, expected result, actual result, etc. The answer A is correct because it suggests adding severity as an additional defect report field. Severity is a measure of the impact of a defect on the system or its users. Severity can help prioritize defects and decide whether they need to be fixed or not. The other answers are incorrect because they suggest adding fields that are already present in the defect report. Test script id is not necessary for a defect report, as it can be inferred from the steps to reproduce. Actual results and expected results are already included in the defect report under what occurred and what should have occurred.

According to the syllabus, dynamic analysis tools are tools that perform testing or analysis by executing the software or a part of it. Dynamic analysis tools can help detect defects or problems that only appear during runtime, such as memory leaks, performance issues, concurrency errors, etc. The answer A is correct because it suggests using a dynamic analysis tool for detecting a memory leak during performance testing. A memory leak is a situation where a code component fails to release memory after it has finished using it, causing memory exhaustion and degradation of performance. A dynamic analysis tool can monitor the memory usage of the code component and identify any memory leaks. The other answers are incorrect because they suggest using tools that are not suitable for detecting memory leaks during performance testing. A test execution tool is a tool that executes test cases automatically or semi-automatically. A configuration management tool is a tool that controls and tracks changes to the software components and documentation. A coverage measurement tool is a tool that measures how much of the code or functionality has been exercised by a test suite.

According to the syllabus, verification is the process of evaluating a product or component to determine whether it satisfies its specified requirements. Validation is the process of evaluating a product or component to determine whether it fulfills its intended use and user expectations. Verification answers the question ''Are we building the product right?'' while validation answers the question ''Are we building the right product?'' Both verification and validation involve providing objective evidence, which means factual, unbiased, and observable information that supports the evaluation. The answer D is correct because it best distinguishes the terms ''validation'' and ''verification''. The other answers are incorrect because they either confuse the terms ''validation'' and ''verification'' or use subjective evidence, which means personal, biased, or unobservable information that does not support the evaluation.

According to the syllabus, a defect is a flaw in a component or system that can cause it to fail to perform its required function. A defect can be introduced in any phase of the software development life cycle, such as requirements, design, coding, testing, or deployment. A possible reason for introducing a defect in software code is rushing to meet a tight deadline to turn code over for testing. This can lead to careless mistakes, incomplete functionality, or poor quality code. The answer A is correct because it is an example of a possible reason for introducing a defect in software code. The other answers are incorrect because they are not reasons for introducing defects in software code, but rather consequences or detection methods of defects.

According to the syllabus, root cause analysis is a technique that aims to identify and address the underlying causes of defects or problems in a process or system. Root cause analysis involves finding the effect (the observable symptom or outcome of the problem), finding the cause (the factor or factors that directly influence the effect), and finding the root cause (the fundamental reason why the cause exists). The answer C is correct because it most accurately reflects this scenario. The incorrect customer discount is the effect and the reason for the requirement error is the root cause. The other answers are incorrect because they either confuse the effect, cause, and root cause or use incorrect terms.

According to the syllabus, the absence-of-errors fallacy is a common misconception that finding and fixing defects will ensure the success of a system. This fallacy ignores the fact that there may be other factors that affect user satisfaction and system value, such as usability, functionality, performance, reliability, security, etc. The answer D is correct because it is an example of the absence-of-errors fallacy. Since testing found very few defects, the system certainly will be successful. This statement assumes that defect detection is the only criterion for system success, which is not true. The other answers are incorrect because they are not examples of the absence-of-errors fallacy, but rather facts or challenges related to testing.