Defect Management Process Flashcards
7 cards from real ISTQB practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Defect Management Process flashcards as text
Which of the following scenarios best illustrates a high-priority, low-severity defect?
Answer: A misspelled company name on the homepage that causes no functional impact but is publicly visible
A misspelling on the homepage has low technical severity but high priority because it is publicly visible and reflects poorly on the organization.
According to ISTQB, who should have the authority to close a defect report after a fix has been applied?
Answer: The tester who originally reported the defect or a designated verifier
The tester or a designated verifier confirms the fix resolves the issue before closing the defect, maintaining independence between fixing and verification.
A defect report states: 'The system sometimes crashes.' Why is this description inadequate?
Answer: It lacks specific, repeatable steps to reproduce the crash and conditions under which it occurs
Vague defect reports that lack reproducible steps prevent developers from investigating and fixing the issue efficiently.
What is the purpose of performing 'root cause analysis' on defects at the end of a project?
Answer: To identify systemic process or skill weaknesses that can be corrected to prevent similar defects in the future
Root cause analysis identifies underlying process or knowledge gaps so that the team can improve practices and prevent recurrence in future projects.
Which defect lifecycle status indicates that a defect has been verified as fixed and no further action is needed?
Answer: Closed
The 'closed' status is the terminal state indicating the defect is confirmed fixed, verified, and requires no further action.
In a defect report, the 'test environment' field should include:
Answer: Hardware, OS, browser/app version, database version, and any other configuration relevant to reproduction
Full environment details allow developers to reproduce the defect in matching conditions, especially important for environment-specific issues.
A project tracks 'defect removal efficiency' (DRE). What does a DRE of 85% indicate?
Answer: 85% of defects present before release were detected and removed before the product reached end users
DRE measures the percentage of total defects that were found and removed during the development and testing phases before reaching production.