Scenario-Based Defect Management Interview Questions & Answers
1. Developer says “Not a bug”. What will you do?
I will recheck the requirement and compare with actual behavior. I will provide clear steps, screenshots/video, and expected vs actual result. If still disagreement, I will involve test lead or product owner.
2. Bug is fixed but still failing. What will you do?
I will retest using same steps and same data. If it still fails, I will reopen the defect with evidence and mention build number.
3. Developer fixed a bug but new issue occurred. What is this called?
It is called regression defect. I will log new defect and also perform regression testing.
4. Bug is found in production. What will you do?
I will analyze why it was missed, check test coverage and improve test cases to avoid same issue in future.
5. What information should a defect contain?
Defect ID, summary, steps to reproduce, expected result, actual result, screenshots, severity, priority, environment, build version.
6. Developer cannot reproduce your bug. What will you do?
I will verify environment, browser, test data and record video or screenshots. I will clearly mention exact steps and conditions.
7. High severity bug found before release. What will you do?
I will inform test lead and product owner immediately and block the release until it is fixed.
8. Same bug is reported by two testers. What will you do?
I will mark one as duplicate and link it with original defect.
9. Bug is rejected as “Works as Designed”. What does it mean?
It means application behavior is as per requirement and not considered a defect.
10. Bug is marked as “Deferred”. What does it mean?
Bug will be fixed in future release, not in current version.
11. What is defect life cycle?
New → Assigned → Open → Fixed → Retest → Closed (or Reopen / Rejected / Deferred based on situation)
12. What is difference between severity and priority?
Severity = impact of defect on system Priority = urgency to fix defect
13. Bug found but requirement is missing. What will you do?
I will confirm with business analyst or product owner and then decide whether to log defect or enhancement.
14. Bug fixed but related functionality is broken. What is this?
It is regression defect and should be logged as new defect.
15. What will you do if build is unstable?
I will perform smoke testing. If critical functions fail, I will reject the build.
16. Developer says “It is data issue, not bug”. What will you do?
I will verify with correct data and confirm whether it is application issue or test data issue.
17. Bug is fixed but UI alignment is broken. Will you log bug?
Yes, it is a usability defect and should be reported.
18. How will you handle invalid defect (false bug)?
I will close it as invalid with proper comment and understanding of correct behavior.
19. What will you do if developer delays bug fix?
I will follow up politely and escalate to test lead if it blocks testing or release.
20. How will you ensure defects are not repeated?
By improving regression test cases, root cause analysis and better test coverage.