Manual Testing :- Defect Life Cycle

Defect Life Cycle :-

It is also called as Bug Life Cycle.
It is a journey of the defect.
When is the tester found any error in the application then it is called as a Defect.
Defeat life cycle contains various stages of defect.
Defect life cycle is nothing but the process from defect identification to closing that effect.
After finding defect by tester that defect is reported in defect report or in a tool. so the starting phase of defect is "New".
Then tester is responsible person to change that status into "Open" Phase. It is an intermediate phase between developer and tester.
When the defect is in open phase then it will be visible to the developer.
Then there are three scenarios for that defect

When developer resolve that defect then he will change the status “Fixed” to “Retest” for Retesting.
After retesting that defect there are two scenario for that particular defect

When retesting is done for a defect and tester confirm that defect is resolve the tester changes status from “Retest” to “Closed”.

After retesting tester check that defect is resolve or not if defeat is not resolve then again he changed status from “Retest” to “Reopen” or Retest fail.

If defect is not valid then developer reject that particular defect and change status to “Rejected”.
When defeat is get rejected then tester check again it is really valid or not if it is mandatory then tester again contact with developer and convey him with strong reason with the help of screenshot or sharing desktop.
If it is not valid then tester change the status from “Rejected” to “Cancel”.
*If developer not accepting that defect then we contact to product owner if defect is very important then we contact to user with permission of product owner*

This is another phase of defect.
If defeat is valid but it has low priority for that particular release then developer put that defect into “Differed” status.