Let us discuss a typical Defect Life Cycle in a Software Development Model.
New – A Defect is in a New status when logged. The Project stakeholders discuss about the defect in the Defect Triage and if it’s valid, move it further to the next stage.
Open/Assigned – The Open status defect is a valid defect and assigned to the Development team to fix it.
Fixed – After successfully fixing the code, the Development team marks the defect as Fixed and is available for the Testing team to retest.
Re-Opened – In case, the fixed defect still displays the earlier deviation from the expected requirement then the Testing team re-assign it to the Development team by marking it as re-opened.
Closed – If the defect is fixed and the requirement is working as expected, the Testing team mark it as Closed.
Deferred – The defects are put into this status, if they are not considered to be fixed in the current release or version of the software. They are marked as deferred to pick them again in the future version/release.
Duplicate – In case the logged defect is already available in the bug report, it’s marked as Duplicate.
Invalid – The defects which do not fall under the project scope or logged because of the lack of tester’s knowledge, can be marked as invalid.
There could be some additional status of the defects as per the Project requirements.
Duplicate, Invalid (Testing) and Re-Opened (Development) count or metrics can be utilised to measure the performance of the Testing and Development teams.
Defect or Bug Life Cycle
New – A Defect is in a New status when logged. The Project stakeholders discuss about the defect in the Defect Triage and if it’s valid, move it further to the next stage.
Open/Assigned – The Open status defect is a valid defect and assigned to the Development team to fix it.
Fixed – After successfully fixing the code, the Development team marks the defect as Fixed and is available for the Testing team to retest.
Re-Opened – In case, the fixed defect still displays the earlier deviation from the expected requirement then the Testing team re-assign it to the Development team by marking it as re-opened.
Closed – If the defect is fixed and the requirement is working as expected, the Testing team mark it as Closed.
Deferred – The defects are put into this status, if they are not considered to be fixed in the current release or version of the software. They are marked as deferred to pick them again in the future version/release.
Duplicate – In case the logged defect is already available in the bug report, it’s marked as Duplicate.
Invalid – The defects which do not fall under the project scope or logged because of the lack of tester’s knowledge, can be marked as invalid.
There could be some additional status of the defects as per the Project requirements.
Duplicate, Invalid (Testing) and Re-Opened (Development) count or metrics can be utilised to measure the performance of the Testing and Development teams.
Follow and Like us:
Defect or Bug Life Cycle
No comments:
Post a Comment