Software Testing Defect Management & Lifecycle Flashcards
6 cards from real Software Testing practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 6 Software Testing Defect Management & Lifecycle flashcards as text
What is the purpose of a defect triage meeting?
Answer: Review, prioritize, and assign open defects for resolution
Defect triage is a collaborative meeting where stakeholders review new defects, assess their priority and severity, and assign them to the appropriate team for resolution.
Which metric tracks the rate at which new defects are found versus defects fixed?
Answer: Defect arrival vs. closure rate
Tracking defect arrival rate versus closure rate reveals whether the team is resolving defects faster than new ones are being discovered.
Defect density is calculated as:
Answer: Total defects divided by the size of the software (e.g., per KLOC)
Defect density measures the number of defects per unit of software size (typically per thousand lines of code), enabling quality comparisons across modules.
What is 'defect removal efficiency' (DRE)?
Answer: The percentage of defects removed before release compared to total defects
DRE = (Defects found before release / Total defects including post-release) × 100%, measuring how effective the testing process is at catching defects before they reach customers.
What is a 'latent defect' in software?
Answer: A defect that exists in the software but has not yet been discovered
A latent defect is one that already exists in the software but remains undetected until specific conditions trigger its manifestation.
After a developer fixes a defect, what should the tester do before closing it?
Answer: Perform verification testing to confirm the fix works and no regression was introduced
Verification testing confirms the fix resolves the original defect, and a quick regression check ensures no new issues were introduced by the change.