Saturday, April 21, 2012

Defect Life Cycle

The duration or time span between the first time bug is found (‘New’) and closed successfully (status: ‘Closed’), rejected, postponed or deferred is called as ‘Bug/DefectLife Cycle’



In the mean time it is assigned various statuses, which are
New, Open, Postpone, Pending Retest, Retest, Pending Reject, Reject, Deferred, and Closed.

The procedure for the above mentioned activities is described below:
·         The QA team will report the bugs/issues found while testing the build With defect status as New/Open.
·         The QA team will then assign the bug to the Offshore Technical Lead/Module Lead.
·         The Offshore Technical Lead/Module Lead will review the bug and reassign it to the appropriate developer
·         The developer attends to the bug and changes the status to Fixed/Deferred/Rejected, along with appropriate remarks
·         The Offshore Technical Lead/Module Lead will then reassign the Fixed and Rejected bugs to the QA team
·         The QA team verifies the bug during Regression Testing. If the status of the bug set by the developer is found to be accurate, the QA team Closes the bug; if the bug still exists the QA team Reopens the bug and reassigns it to the Lead, along with appropriate remarks.
·         After Regression Testing and before Build Release, the QA team will prepare a Test Summary Log, which shows a summary of the status of all the bugs found in the build.