The program code containing the detected defect should be sent to the developers for correcting. It is necessary to closely monitor the stages of correction, so as not to lose sight of the defect itself. One effective way to track a defect is to clearly identify explicit states that a defect can sit in while being tracked prior to the final test. Each state should be unambiguous and have a set of definitions for entry and exit criteria of the test process.
Definitions of defect statuses. The table below shows an example of how to define defect statuses. The status names can vary from company to company, there are also possible additional states that are not specified in this table. It shows a generalized set of names and states, which, perhaps, should be used as a starting point for creating a defect tracking system from scratch.
Table. Definition of defect statuses
|Category||Liability for Defects||Description|
A defect is detected during the test, and documented in the report, but the developer is not ordered to eliminate the problem.
The developer is ordered to fix the problem, and the relevant work is underway.
|Defer||Development team||It has been decided to defer defect fixes till the next product releases.|
|Trash||Defect analysis team|
The defect is detected incorrectly, the software product is working as expected, there are other possible reasons due to which it is decided not to do anything to fix the defect.
|Repair||Development team||The developer has identified and eliminated the main cause of the defect and conducted preliminary testing to ensure that the problem has been resolved.|
The testing specialist has verified the fixes, using the same test methodology and the same testing tools that allowed him to initially detect the defect.
Resorting to offshore software testing services you are going to pay less for the same quality work done by near- or on-shore qa specialists. Why to spend more money on expensive professionals if there is the possibility to hire cheaper employees with the same qualification?
Tracking a defect throughout its life cycle, from its detection to elimination and verifying the correctness of the fixes, shows that it changes its state according to some set of rules. A defect is detected during the revision process or during system testing and is entered into the defect tracking system, being in the status “new”. It is assigned a severity level, and after that it is submitted to the defect analysis group for consideration.
Comments are closed.