What is Defect management?
Basically, defect management (DM) is the process of detecting bugs and then fixing them. It is a part of software testing process. The primary purpose of DM process is to prevent defects. It is kinda like “bug tracking”, a process of tracking bugs and removing them from our software product.
The process of DM usually includes four main steps:
- Defect detecting: so, find the defects!
- Dedicated to the formulation of bug reports: document all the necessary information about defects involved in the software product, which includes data on the type of bugs, possible ways of its corrections, priorities, etc..
- Defect fixing: fix them!
- The bug/defect list is created: this is the document that contains information about all bugs that occurred during the project’s performance.
Defect Management Lifecycle
Here is the lifecycle of DM. Note that DMLC is different from DM.
The lifecycle of DM starts from when a defect is found for the first time. So now it has a state as “new”, which means that the bug is not yet approved. Then, the tester will post that particular defect/bug, and testing lead will approve that the defect is genuine and the state will be changed to “open”.
Once the state of the defect is changed to “open”, this defect will be assigned to corresponding developer or development team to fix is. After the defect is fixed, it will be assigned back to the testing team for the next round of testing. If the defect is not present, the tester will approve that the defect is fixed and verified. Otherwise, the defect will be re-open and fixed again.
What does “referred” means? That is, this bug or defect is expected to be fixed in future releases. For example, the use case states that customers want a “1+1=3”, and the system is doing in the same way. Under this situation, a tester should pass this test. However, based on our common sense, it is impossible to see that 1+1=3. So we pass this test, but give feedback to the BA and say that there are no defects about this one, but there may have something wrong as 1+1=2. So now this defect has been “deferred”, and the BA will go back and check their document again.