1. Overview: Why Defect Life Cycle Knowledge Is Critical in Software Testing
In real-world projects, finding a bug is only 30% of a tester’s job. The remaining 70% lies in managing that defect correctly across its entire life cycle—from discovery to closure. This is why interviewers heavily focus on defect life cycle in software testing interview questions, especially for experienced roles.
Understanding the defect life cycle helps testers:
- Communicate effectively with developers and stakeholders
- Reduce defect leakage into production
- Improve release quality and predictability
- Perform meaningful Root Cause Analysis (RCA)
- Align testing activities with Agile, DevOps, and CI/CD practices
This article is designed as end-to-end interview material for:
- Freshers & junior testers
- Manual & automation testers
- Senior QA engineers & test leads
2. Defect Life Cycle in Software Testing – Basic Interview Questions (Q1–Q20)
Q1. What is a defect?
Answer:
A defect (or bug) is a deviation between expected behavior and actual behavior of a software application.
Q2. What is the defect life cycle?
The defect life cycle describes the various states a defect goes through from identification to closure.
Q3. Why is the defect life cycle important?
- Ensures proper defect tracking
- Improves communication
- Prevents missed or ignored bugs
- Helps in release decision-making
Q4. What are the common defect states?
Typical Defect Life Cycle States:
- New
- Assigned
- Open
- Fixed
- Retest
- Verified
- Closed
Q5. What happens in the “New” status?
A tester logs a defect for the first time with complete details.
Q6. What does “Assigned” status mean?
The defect is assigned to a developer or team for fixing.
Q7. What is “Open” status?
The developer starts working on the defect.
Q8. What is “Fixed” status?
Developer claims the defect has been fixed and moved for retesting.
Q9. What is “Retest”?
Tester re-executes the test case to verify the fix.
Q10. What is “Verified” status?
Tester confirms the defect is fixed as expected.
Q11. What is “Closed” status?
Defect is formally closed after successful verification.
Q12. What is a “Reopened” defect?
If a defect persists after fixing, it is reopened.
Q13. What is “Deferred” status?
Defect is postponed to a future release due to low priority or constraints.
Q14. What is “Rejected” defect?
Developer rejects the defect due to:
- Invalid issue
- Duplicate
- As per design
Q15. What is “Duplicate” defect?
Defect already exists in the system.
Q16. What is “Not a Bug”?
Behavior matches requirement or design specification.
Q17. What is defect severity?
Severity indicates technical impact of a defect.
Q18. What is defect priority?
Priority indicates business urgency to fix a defect.
Q19. Severity vs Priority example
| Scenario | Severity | Priority |
| Payment failure | Critical | High |
| UI alignment issue | Low | Low |
| Broken link on homepage | Medium | High |
Q20. Who manages the defect life cycle?
QA team owns tracking; entire team owns quality.
3. Defect Life Cycle – Intermediate Interview Questions (Q21–Q45)
Q21. What are mandatory fields in a defect report?
- Defect ID
- Summary
- Steps to reproduce
- Expected & actual result
- Severity & priority
- Environment
Q22. What makes a good defect report?
- Clear title
- Reproducible steps
- Screenshots/logs
- Business impact
Q23. What is defect triage?
A meeting to review, prioritize, and assign defects.
Q24. Who attends defect triage?
- QA
- Development
- Product Owner
- Project Manager
Q25. What is defect aging?
Time duration a defect remains open.
Q26. Why is defect aging tracked?
- Identify bottlenecks
- Improve SLA compliance
Q27. What is defect leakage?
Defects missed during testing and found in production.
Q28. How do you reduce defect leakage?
- Shift-left testing
- Automation regression
- Strong test coverage
- RCA on escaped defects
Q29. What is Defect Density?
Number of defects per module or size of code.
Q30. What is Defect Removal Efficiency (DRE)?
Percentage of defects removed before production.
Q31. What is defect clustering?
Most defects are found in few critical modules.
Q32. What is bug life cycle vs defect life cycle?
Both terms are used interchangeably in industry.
Q33. What is the impact of poor defect management?
- Missed bugs
- Release delays
- Customer dissatisfaction
Q34. How does defect life cycle differ in Agile?
Defects are:
- Logged per sprint
- Prioritized in backlog
- Fixed continuously
Q35. What is a blocker defect?
A defect that halts testing or development.
Q36. What is cosmetic defect?
UI-related issue with minimal functional impact.
Q37. What is environment-specific defect?
Occurs only in specific OS/browser/config.
Q38. What is data-related defect?
Incorrect data creation, update, or retrieval.
Q39. What is configuration defect?
Issue due to incorrect environment setup.
Q40. What is regression defect?
A defect introduced due to new code changes.
Q41. How does automation help defect life cycle?
- Faster regression
- Early defect detection
- Reduced defect aging
Q42. How are API defects different?
They require:
- Status code validation
- Payload analysis
- Contract verification
Q43. What is defect reopening rate?
Percentage of reopened defects.
Q44. What does high reopening rate indicate?
- Poor fix quality
- Incomplete requirements
Q45. What is defect trend analysis?
Studying defect patterns over time.
4. Scenario-Based Defect Life Cycle Interview Questions (Q46–Q70)
Q46. Developer says “Not a bug”. What do you do?
Sample Answer:
- Recheck requirement
- Provide screenshots/logs
- Explain business impact
- Escalate if needed
Q47. A defect is fixed but still failing in QA. What next?
- Reopen defect
- Attach evidence
- Update severity if needed
Q48. Multiple defects found just before release. What do you do?
- Prioritize critical defects
- Defer low-risk issues
- Communicate release risk
Q49. A production defect occurs. What is your approach?
- Assess impact
- Inform stakeholders
- Reproduce issue
- RCA
- Prevent recurrence
Q50. RCA example for escaped defect
Issue: Duplicate orders
Root Cause: Missing idempotency
Fix: Backend validation
Prevention: Contract test added
Q51. How do you handle deferred defects?
- Track in backlog
- Review every release
Q52. What if a defect is ignored?
- Escalate with data
- Document risk
Q53. How do you manage defects under tight timelines?
- Risk-based triage
- Focus on high-severity issues
Q54. How do you handle environment-related defects?
- Validate config
- Raise infra ticket
Q55. What if defect cannot be reproduced?
- Collect logs
- Increase logging
- Narrow scope
Q56. How do you analyze defect root cause?
- Requirement gap
- Code issue
- Data/environment issue
Q57. How do you prevent recurring defects?
- RCA
- Add regression test
- Improve reviews
Q58. How does Agile impact defect prioritization?
Priority changes dynamically based on sprint goals.
Q59. How do you manage defects in CI/CD?
- Automated test failures logged
- Build blockers enforced
Q60. How do you handle flaky defects?
- Identify pattern
- Stabilize environment
Q61. How do you communicate defect risk to management?
Using impact, not technical jargon.
Q62. How do you analyze defect trends?
- Module-wise
- Sprint-wise
Q63. What if business wants to release with known defects?
- Explain risk
- Get sign-off
- Document acceptance
Q64. What is defect leakage RCA?
Analyzing why defect escaped testing.
Q65. How do you improve defect turnaround time?
- Clear triage
- Better defect reporting
Q66. How do you handle duplicate defects?
- Link defects
- Close duplicates
Q67. What is invalid defect?
Reported issue that is not actually a defect.
Q68. What is defect backlog?
List of open defects waiting to be addressed.
Q69. How do you track defect SLA?
Using aging and status metrics.
Q70. What defines a healthy defect life cycle?
- Low aging
- Low reopening
- Low leakage
5. Test Case Writing Examples (Defect-Oriented)
Login Feature – Sample Test Cases
| TC ID | Scenario | Expected Result |
| TC01 | Valid login | Success |
| TC02 | Invalid password | Error |
| TC03 | SQL injection | Access denied |
| TC04 | Brute force | Account lock |
6. Defect Report Example (Industry Standard)
Title: Duplicate payment on retry
Environment: QA | Chrome 124
Steps:
- Initiate payment
- Retry after timeout
Actual Result: Amount deducted twice
Expected Result: Single transaction
Severity: Critical
Priority: High
7. SDLC, STLC & Defect Life Cycle Mapping
| Phase | Defect Activity |
| Requirement | Requirement defects |
| Design | Design gaps |
| Development | Code defects |
| Testing | Functional defects |
| Production | Escaped defects |
8. Tools Used in Defect Management
- Jira – Defect tracking & workflow
- TestRail – Test case linkage
- Selenium – Regression detection
- Postman – API defect validation
- Jenkins – CI defect visibility
9. Domain-Based Defect Life Cycle Examples
Banking
- Transaction mismatches
- Compliance defects
Insurance
- Rule calculation defects
E-Commerce
- Payment & checkout defects
Healthcare
- Data integrity defects
10. Quick Revision Sheet – Defect Life Cycle
- Bug ≠ fixed until verified
- Severity ≠ Priority
- RCA prevents recurrence
- Defect life cycle reflects team maturity
11. FAQ – Defect Life Cycle in Software Testing Interview Questions
Q. Is defect life cycle same in all companies?
Concept is same; statuses may vary.
Q. Who closes defects?
Usually QA, sometimes QA lead.
Q. Are all defects fixed?
No, some are deferred or rejected.