CAST Defect Management Lifecycle 2 — Questions and Answers
Question 1: A tester logs a defect but cannot reliably reproduce it on later attempts. What status best fits this defect?
- Cannot Reproduce (Correct answer)
- Closed
- Verified
- Reopened
Correct answer: Cannot Reproduce
When a defect cannot be consistently reproduced, it is marked 'Cannot Reproduce' pending more information.
Question 2: Who is primarily responsible for verifying that a fixed defect is actually resolved before it is closed?
- The tester who reported it (Correct answer)
- The project sponsor
- The end user
- The build server
Correct answer: The tester who reported it
The reporting tester typically re-tests the fix to confirm resolution before closing.
Question 3: A defect is marked 'Deferred.' What does this most likely mean?
- The fix is postponed to a future release (Correct answer)
- The defect is invalid
- The defect was already fixed
- The defect is a duplicate
Correct answer: The fix is postponed to a future release
'Deferred' means the team agreed to address the defect in a later release rather than the current one.
Question 4: Which document or field captures the exact steps needed to recreate a defect?
- Steps to reproduce (Correct answer)
- Root cause analysis
- Release notes
- Test summary report
Correct answer: Steps to reproduce
The 'steps to reproduce' field gives developers the precise sequence to trigger the defect.
Question 5: When two testers report the same underlying issue separately, the later report should be marked as what?
- Duplicate (Correct answer)
- Rejected
- Deferred
- Reopened
Correct answer: Duplicate
A second report of an already-logged issue is closed as a 'Duplicate' and linked to the original.
Question 6: A developer reviews a reported defect and determines the application behaves as designed. What status applies?
- Rejected / Not a Defect (Correct answer)
- Fixed
- Reopened
- Deferred
Correct answer: Rejected / Not a Defect
If behavior matches the requirements, the defect is rejected as 'Not a Defect' or 'Working as Designed'.
Question 7: What is the correct status transition immediately after a developer completes a code change to address a defect?
- Fixed / Ready for Retest (Correct answer)
- Closed
- New
- Duplicate
Correct answer: Fixed / Ready for Retest
After fixing, the defect moves to 'Fixed/Ready for Retest' so the tester can verify it.
CAST Defect Management Lifecycle 2
A tester logs a defect but cannot reliably reproduce it on later attempts.
What status best fits this defect?