BUG LIFE CYCLE
In software testing is the specific set of states that defect or bug goes through in its entire lifecycle. The purpose of Defect life cycle is to easily coordinate and communicate current status of defect which changes to various assignees and make the defect fixing process systematic and efficient.
New: When a new defect is logged and posted for the first time. It is assigned a status as NEW.
Assigned: Once the bug is posted by the tester, the lead of the tester approves the bug and assigns the bug to the developer team.
Open: The developer starts analysing and works on the defect fix.
Fixed: When a developer makes a necessary code change and verifies the change, he or she can make bug status as "Fixed."
Pending retest: Once the defect is fixed the developer gives a particular code for retesting the code to the tester. Since the software testing remains pending from the testers end, the status assigned is "pending retest."
Retest: Tester does the retesting of the code at this stage to check whether the defect is fixed by the developer or not and changes the status to "Re-test."
Verified: The tester re-tests the bug after it got fixed by the developer. If there is no bug detected in the software, then the bug is fixed, and the status assigned is "verified."
Reopen: If the bug persists even after the developer has fixed the bug, the tester changes the status to "reopened". Once again, the bug goes through the life cycle.
Closed: If the bug is no longer exists then tester assigns the status "Closed."
Duplicate: If the defect is repeated twice or the defect corresponds to the same concept of the bug, the status is changed to "duplicate."
Rejected: If the developer feels the defect is not a genuine defect then it changes the defect to "rejected."
Deferred: If the present bug is not of a prime priority and if it is expected to get fixed in the next release, then status "Deferred" is assigned to such bugs
Not a bug: If it does not affect the functionality of the application then the status assigned to a bug is "Not a bug".What is a Defect:
The variation between the actual results and expected results is known as defect.
If a developer finds an issue and corrects it by himself in the development phase, then it is called defect.
What is a Bug:
If testers find any mismatch in the application in the testing phase, then they call it as Bug.
As mentioned earlier there is a contradiction in the usage of Bug and Defect.
What is an Error:
We cannot compile or run a program due to coding mistake in a program. If a developer unable to successfully compile or run a program, then they call it as an error.
What is a failure:
Once the product is deployed and customers find any issue then they call the product as a failure product. After release if an end user finds an issue then that issue is called as failure.
PRIORITY AND SEVERITY
Priority is defined as the order in which a defect should be fixed. Higher the priority the sooner the defect should be resolved.
PRIORITY TYPES
Types of Priority of bug/defect can be categorized into three parts:
Low: The Defect is an irritant, but repair can be done once the more serious Defect has been fixed
Medium: During the normal course of the development activities defect should be resolved. It can wait until a new version is created.
High: The defect must be resolved as soon as possible as it affects the system severely and cannot be used until it is fixed
BUG SEVERITY
Bug Severity or Defect Severity in testing is a degree of impact a bug or a Defect has on the software application under test. A higher effect of bug/defect on system functionality will lead to a higher severity level.
TYPES OF SEVERITY
In Software Testing, Types of Severity of bug/defect can be categorized into four parts:
Critical: This defect indicates complete shut-down of the process, nothing can proceed further
Major: It is a highly severe defect and collapses the system. However, certain parts of the system remain functional.
Medium: It causes some undesirable behaviour, but the system is still functional
Low: It will not cause any major break-down of the system