Defect Management Process Flashcards

During a defect triage meeting, the team is discussing a newly reported defect. Which of the following is the PRIMARY objective of this meeting?

Answer: To evaluate, prioritize, and assign the defect for resolution.

The primary purpose of a defect triage meeting is to review, evaluate, and prioritize reported defects. This includes deciding on the severity and priority, determining if it's a valid defect, and assigning it to the appropriate team or developer for further action. While root cause analysis and assigning the defect are parts of the overall defect management process, the key activity in triage is the collective decision-making on the defect's priority and assignment.

A tester logs a defect and includes a unique ID, a title, steps to reproduce, actual results, and expected results. According to ISTQB, which of the following essential pieces of information is missing from this defect report?

Answer: Identification of the test object (what was tested) and the test environment.

A standard ISTQB-compliant defect report should include identification of the test item (the software or component being tested) and the environment in which the defect was found. This information is crucial for developers to reproduce the issue accurately. While developer assignment and fix estimates are added later in the lifecycle, and a link to a script is helpful but not always mandatory, the test object and environment are considered fundamental initial details.

A defect is discovered and logged. The development team analyzes it and determines that it is a valid issue, but the business decides that the feature it impacts will be removed in the next major release. The cost of fixing it now outweighs the benefit. Which of the following is the MOST appropriate status for this defect?

Answer: Deferred

A 'Deferred' status indicates that the defect is acknowledged as valid, but its resolution is intentionally postponed to a future release. This is a common decision when the fix is low priority, high cost, or related to a feature that is being deprecated. 'Rejected' means the defect is not considered genuine. 'Closed' implies it has been resolved and verified. 'Fixed' is a status used by developers before the fix is verified by testers.

Which of the following describes the main goal of performing root cause analysis (RCA) as part of the defect management process?

Answer: To identify the underlying cause of a defect to prevent similar future defects.

Root Cause Analysis (RCA) is a systematic process aimed at identifying the fundamental cause of a problem, rather than just addressing its symptoms. In defect management, the goal is to understand why the defect was introduced in the first place, enabling process improvements that prevent similar defects from occurring in the future. It focuses on process improvement, not on blaming individuals.

A defect has been fixed by the developer and is now ready for the tester to verify. Which stage of the standard defect lifecycle occurs IMMEDIATELY after the tester successfully verifies the fix?

Answer: Closed

After a defect is fixed, the tester performs confirmation testing (re-testing) to verify the fix. If the verification is successful and the defect is resolved, the next and final state in the lifecycle is 'Closed'. 'Reopened' would be the status if the verification failed. 'Assigned' and 'In Progress' are earlier states in the lifecycle.

A project manager is analyzing defect reports to gain insights into the quality of the product and the efficiency of the development process. Which of the following is NOT a primary objective of a defect report?

Answer: To provide ideas for new features for the product.

The primary objectives of a defect report are to provide information for fixing the issue, track product quality, and offer insights for process improvement. While analyzing defect trends might indirectly inspire new features (e.g., by highlighting user difficulties), the explicit purpose of a defect report is to document a deviation from expected behavior, not to propose new functionality.