Error, Mistake, Defect, Bug, Fault, and Failure in Software Testing, Software Test Life Cycle, Defect Life Cycle, and Defect Management.
Defect and Bug in Software Testing
Error, Mistake, Defect, Bug, Fault, and Failure in Software Testing,
Software Application Life Cycle
| Software Development | Software Testing | Production |
| Error | Defect | Failure |
| Mistake | Bug | |
| Fault |
1. Error or Mistake:
Error is a human action that produces an incorrect result. It is deviation from actual and expected value. The mistakes made by programmer is known as an ‘Error’.
2. Bug:
A Bug is the result of a coding Error or Fault in the program which causes the program to behave in an unintended manner.
3. Defect or Fault:
A Defect is a deviation from the Requirements. A Software Defect is a condition in a software product which does not meet a software requirement or end-user expectations.
Bug vs. Defect
A Bug is the result of a coding Error and A Defect is a deviation from the Requirements. A defect does not necessarily mean there is a bug in the code,
5. Failure:
If an end-user detects an issue in the product, then that particular issue is called a failure.
A Sample Defect report or Bug report:
Defect ID – Every bug or defect has it’s unique identification number
Defect Description – This includes the abstract of the issue.
Product Version – This includes the product version of the application in which the defect is found.
Detail Steps – This includes the detailed steps of the issue with the screenshots attached so that developers can recreate it.
Date Raised – This includes the Date when the bug is reported
Reported By – This includes the details of the tester who reported the bug like Name and ID
Status – This field includes the Status of the defect like New, Assigned, Open, Retest, Verification, Closed, Failed, Deferred, etc.
Fixed by – This field includes the details of the developer who fixed it like Name and ID
Date Closed – This includes the Date when the bug is closed
Severity – Based on the severity (Critical, Major or Minor) it tells us about impact of the defect or bug in the software application
Priority – Based on the Priority set (High/Medium/Low) the order of fixing the defect can be made.
Follow me on social media:
