BUG LIFE CYCLE:

What is Bug/Defect?
Simple Wikipedia defiiti! !f Bug is: A computer bug is an error, flaw, mistake, failure, or
fault in a computer program that prevents it from working correctly or produces an incorrect result.
Bugs arise from mistakes and errors, made by people, in either a programs source code or its
design.
"the# defiiti!s ca $e:
An unwanted and unintended property of a program or piece of hardware, especially one that causes
it to malfunction.
!#
A fault in a program, which causes the program to perform in an unintended or unanticipated
manner.
Lastly the general definition of bug is failure to conform to specifications.
!f you want to detect and resolve the defect in early development stage, defect tracking and software
development phases should start simultaneously.
"e will discuss more on "riting effective bug report in another article. Lets concentrate here on
bug#defect life cycle.
Life c%cle !f Bug:
&' L!g e( defect
"hen tester logs any new bug the madat!#% fields are
Build version, $ubmit %n, &roduct, 'odule, $everity, $ynopsis and (escription to )eproduce
!n above list you can add some !pti!al fields if you are using manual Bug submission template
*hese %ptional +ields are ,ustomer name, Browser, %perating system, +ile Attachments or
screenshots.
)he f!ll!(ig fields #emai eithe# specified !# $lak:
!f you have authority to add bug $tatus, &riority and -Assigned to fields them you can specify these
fields. %therwise *est manager will set status, Bug priority and assign the bug to respective module
owner.
L!!k at the f!ll!(ig Bug life c%cle:
.,lick on the image to view full si/e0 )ef Bug/illa bug life cycle
*he figure is 1uite complicated but when you consider the significant steps in bug life cycle you
will get 1uick idea of bug life.
%n successful logging the bug is reviewed by (evelopment or *est manager. *est manager can set
the bug status as %pen, can Assign the bug to developer or bug may be deferred until ne2t release.
"hen bug gets assigned to developer and can start working on it. (eveloper can set bug status as
wont fi2, ,ouldnt reproduce, 3eed more information or -+i2ed.
!f the bug status set by developer is either -3eed more info or +i2ed then 4A responds with
specific action. !f bug is fi2ed then 4A verifies the bug and can set the bug status as verified closed
or )eopen.
Bug status desc#ipti!:
*hese are various stages of bug life cycle. *he status caption may vary depending on the bug
tracking system you are using.
&' *e(: "hen 4A files new bug.
+' Defe##ed: !f the bug is not related to current build or can not be fi2ed in this release or bug is not
important to fi2 immediately then the pro5ect manager can set the bug status as deferred.
,' -ssiged: -Assigned to field is set by pro5ect lead or manager and assigns bug to developer.
.' /es!l0ed/Fi1ed: "hen developer makes necessary code changes and verifies the changes then
he#she can make bug status as -+i2ed and the bug is passed to testing team.
2' C!uld !t #ep#!duce: !f developer is not able to reproduce the bug by the steps given in bug
report by 4A then developer can mark the bug as -,3). 4A needs action to check if bug is
reproduced and can assign to developer with detailed reproducing steps.
3' *eed m!#e if!#mati!: !f developer is not clear about the bug reproduce steps provided by 4A
to reproduce the bug, then he#she can mark it as 3eed more information. !n this case 4A needs to
add detailed reproducing steps and assign bug back to dev for fi2.
4' /e!pe: !f 4A is not satisfy with the fi2 and if bug is still reproducible even after fi2 then 4A
can mark it as -)eopen so that developer can take appropriate action.
5 ' Cl!sed: !f bug is verified by the 4A team and if the fi2 is ok and problem is solved then 4A can
mark bug as -,losed.
6' /e7ected/I0alid: $ome times developer or team lead can mark the bug as )e5ected or invalid if
the system is working according to specifications and bug is 5ust due to some misinterpretation.