Bug life cycle

Posted In | Bug Defect tracking, Software Testing Templates, Testing Life cycle What is Bug/Defect? Simple Wikipedia definition of 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. Other definitions can be: An unwanted and unintended property of a program or piece of hardware, especially one that causes it to malfunction. or 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. If you want to detect and resolve the defect in early development stage, defect tracking and software development phases should start simultaneously. We will discuss more on Writing effective bug report in another article. Lets concentrate here on bug/defect life cycle. Life cycle of Bug: 1) Log new defect When tester logs any new bug the mandatory fields are: Build version, Submit On, Product, Module, Severity, Synopsis and Description to Reproduce In above list you can add some optional fields if you are using manual Bug submission template: These Optional Fields are: Customer name, Browser, Operating system, File Attachments or screenshots. The following fields remain either specified or blank: If you have authority to add bug Status, Priority and Assigned to fields them you can specify these fields. Otherwise Test manager will set status, Bug priority and assign the bug to respective module owner. Look at the following Bug life cycle:

[Click on the image to view full size] Ref: Bugzilla bug life cycle The figure is quite complicated but when you consider the significant steps in bug life cycle you will get quick idea of bug life. On successful logging the bug is reviewed by Development or Test manager. Test manager can set the bug status as Open, can Assign the bug to developer or bug may be deferred until next release. When bug gets assigned to developer and can start working on it. Developer can set bug status as wont fix, Couldnt reproduce, Need more information or Fixed. If the bug status set by developer is either Need more info or Fixed then QA responds with specific action. If bug is fixed then QA verifies the bug and can set the bug status as verified closed or Reopen. Bug status description: These are various stages of bug life cycle. The status caption may vary depending on the bug tracking system you are using. 1) New: When QA files new bug. 2) Deferred: If the bug is not related to current build or can not be fixed in this release or bug is not important to fix immediately then the project manager can set the bug status as deferred. 3) Assigned: Assigned to field is set by project lead or manager and assigns bug to developer. 4) Resolved/Fixed: When developer makes necessary code changes and verifies the changes then he/she can make bug status as Fixed and the bug is passed to testing team. 5) Could not reproduce: If developer is not able to reproduce the bug by the steps given in bug report by QA then developer can mark the bug as CNR. QA needs action to check if bug is reproduced and can assign to developer with detailed reproducing steps. 6) Need more information: If developer is not clear about the bug reproduce steps provided by QA to reproduce the bug, then he/she can mark it as Need more information. In this case QA needs to add detailed reproducing steps and assign bug back to dev for fix.

7) Reopen: If QA is not satisfy with the fix and if bug is still reproducible even after fix then QA can mark it as Reopen so that developer can take appropriate action. 8 ) Closed: If bug is verified by the QA team and if the fix is ok and problem is solved then QA can mark bug as Closed. 9) Rejected/Invalid: Some times developer or team lead can mark the bug as Rejected or invalid if the system is working according to specifications and bug is just due to some misinterpretation. Defect Life Cycle is the Cycle thru which a defect goes starts when defect found & ends when defect is closed after ensuring its not reproduced.Defect Life cycle is related to Bug found during testing so it doesn depend on Manual & Automated Testing. Phases of Defect Life Cycle is 1. New : When Defect disccovered. 2.Open: When defect is addressed to the developer. It may then be Rejected, said to be duplicate or deferred. 3. Fix : when it is fixed or defect solved by developer. 4.Close : After defect addressed by developer it comes to Tester to Test, once assured its no more a defect its is Close phase. There are more phases to this if it is to be discussed in too details but on primary level this is the right answere.

Proposed,Active,Fixed ,Resolved,Rejected and closed Proposed : New bug raised by the tester and assigned to Triage Active : Dev team Accepts to fix this defect and assigned to a developer. Fixed : Developer fixes the defect and released code fix for Unit testing. Reolved : Developer completes unit testing and Release the fix to System test Environment. Rejected : When the fix provided doesnt work as expected or The problem still persists . Closed : Tester closes the defects after system testing completed and the issue/Bug was fixed.

Posted by: Sravan Kumar Dunna

Contact Sravan Kumar Dunna

Bug life cycle includes following stages:1)New:- when tester first encounter with Bug then status called as New 2)Assigned:-Once Tester encounter with bug Team lead or Tester will assign it to Developer team and change status as Assigned. 3)Open:-Once Developer start working onto the Bug he will make the status as Open. 4)Fixed:- Once the Developer fixed the code then he change the status as Fixed. 5)Pending Retest:- After Bug is fixed developer will send this issue back to Tester for Retest and stauts change to Pending Retest. 6)Retest:- Once tester will start resteting onto his Bug then he change status as Retest. 7)Fixed:-Once Tester Retested the Bug and found that bug is fixed and issue is no more the he will go ahead and change the status to Fixed. 8)Reopen:-If Tester Retested the bug and found that issue still persist then he will change the status to Reopen.

Posted by: Atul saurabh

Contact Atul saurabh

(1)New:When a Tester Enters the defect in the defect tracking tool against the developer. (2)Assigned:When Tester assigns the defect to the concerned developer. (3)UI(UnderInvestigation):Once the developer starts analyzing the defect changes the status of the defect to (UI).if he thinks that its a defect he changes it to (Coding in Progress) and if he feels that its working as per design then he changes the status of the defect to (RETURNED) and sends it back to the tester. (4)RFT:once the developer fixes the defect he assigns it back to the tester and changes the status to RFT. (5)Return/Closed:after tester receives the defect back from the developer he tests it,and if it works fine then he closes the defect else he returns it back to the developer by change the status to (RETURN). and finally the status of the defect would go as CLOSED by the tester

Posted by: kondal

Contact kondal

Defect life cycle follows these steps NEW:When ever we are raise the defect newly in that time the status will be new OPEN:If the devoloper accepting the defect he is working on that defect to fix. at that time the status of the defect is open REJECT:when the devoloper didn't accept the defect which is raising by the tester in that time status is reject FIX:Once the devoloper has fix that defect in that time status of the defect is fix REOPEN:if the fixed defect is failed again tester will change the status of the defect is reopen CLOSE:if the fix defect is working fine then the ststus of the defect is closed this is defect life cycle What is Bug/Defect? Simple Wikipedia definition of 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. Other definitions can be: An unwanted and unintended property of a program or piece of hardware, especially one that causes it to malfunction. or 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. If you want to detect and resolve the defect in early development stage, defect tracking and software development phases should start simultaneously. We will discuss more on Writing effective bug report in another article. Lets concentrate here on bug/defect life cycle. Life cycle of Bug: 1) Log new defect When tester logs any new bug the mandatory fields are:

Build version, Submit On, Product, Module, Severity, Synopsis and Description to Reproduce In above list you can add some optional fields if you are using manual Bug submission template: These Optional Fields are: Customer name, Browser, Operating system, File Attachments or screenshots. The following fields remain either specified or blank: If you have authority to add bug Status, Priority and Assigned to fields them you can specify these fields. Otherwise Test manager will set status, Bug priority and assign the bug to respective module owner. Look at the following Bug life cycle:

[Click on the image to view full size] Ref: Bugzilla bug life cycle The figure is quite complicated but when you consider the significant steps in bug life cycle you will get quick idea of bug life. On successful logging the bug is reviewed by Development or Test manager. Test manager can set the bug status as Open, can Assign the bug to developer or bug may be deferred until next release. When bug gets assigned to developer and can start working on it. Developer can set bug status as wont fix, Couldnt reproduce, Need more information or Fixed. If the bug status set by developer is either Need more info or Fixed then QA responds with specific action. If bug is fixed then QA verifies the bug and can set the bug status as verified closed or Reopen. Bug status description: These are various stages of bug life cycle. The status caption may vary depending on the bug tracking system you are using. 1) New: When QA files new bug. 2) Deferred: If the bug is not related to current build or can not be fixed in this release or bug is

not important to fix immediately then the project manager can set the bug status as deferred. 3) Assigned: Assigned to field is set by project lead or manager and assigns bug to developer. 4) Resolved/Fixed: When developer makes necessary code changes and verifies the changes then he/she can make bug status as Fixed and the bug is passed to testing team. 5) Could not reproduce: If developer is not able to reproduce the bug by the steps given in bug report by QA then developer can mark the bug as CNR. QA needs action to check if bug is reproduced and can assign to developer with detailed reproducing steps. 6) Need more information: If developer is not clear about the bug reproduce steps provided by QA to reproduce the bug, then he/she can mark it as Need more information. In this case QA needs to add detailed reproducing steps and assign bug back to dev for fix. 7) Reopen: If QA is not satisfy with the fix and if bug is still reproducible even after fix then QA can mark it as Reopen so that developer can take appropriate action. 8 ) Closed: If bug is verified by the QA team and if the fix is ok and problem is solved then QA can mark bug as Closed. 9) Rejected/Invalid: Some times developer or team lead can mark the bug as Rejected or invalid if the system is working according to specifications and bug is just due to some misinterpretation.

Post Resume: Click here to Upload your Resume & Apply for Jobs IP Logged