Identifying defects in system is a blend of art and science. In this blog post, we will see about defects life cycle to know how defects travels from tester to developer to tester.
Assume, you bought a packet of pencils, in which there is a broken item. Or you bought a pack of 6 drinking glasses, in which one is broken. Above are the examples of defective products. Everyone wants value product for their money, isn’t it? Similarly, every application should be a defect-free to end users. If there is any conflict between the requirements and the end product, then we can say there are defects exist.
What is Defect?
In software terms, variance from software requirement specifications or any unintended events occurs during testing can be called as Defects.
Bug in the code, incorrect functionality, unwanted functionalities, and errors and so on.
Defects tracking is the process of identifying, logging, prioritizing and categorizing to assist developers to fix defects with in stipulated amount of time.
Defects tracking tool helps testers to log, prioritize, categorize, track the status, and prepare the report and metrics of defects.
Below is the simple representation of defects life cycle.
Status, Action and Description
When tester identifies a new defect in the system, the inception status of the defect is NEW. Defect analysis will be performed by test team lead to validate the defect. If it is a valid defect, then team lead checks whether it is in-scope or not. If it is in-scope, then the defect duplicate check will be performed. If all is well, then the defect status will be changed to ASSIGNED to respective developer.
If it is not in-scope, then the status will be DEFERRED. If it is duplicate defect, then the status will be changed to DUPLICATE.
Once the defect is fixed, developer changes the status to FIXED and assigns to tester as RETEST. If retest successful, then the defect status will be changed to CLOSED, else the status will be changed to REOPEN; developer needs to relook the issue.