Priya

• Sep 30th, 2005

 

New-when new bug has been found

Open-when developers are still working on the bug

fixed- when developer has fixed the bug he assigns this status

Closed-After retesting the bug and when there are no more issues QA assigns it as Closed status

Reopen- if the defect is not satisfied or defect is not fixed

Reject-developer may reject the defect with proper reasons attached if he thinks that this is not a defect

anu

• Oct 3rd, 2005

 

The bug cycle consists of 4 main stages those are:

1.New:- When you find a new bug in the application which was not detected previously.

2.Open:-Open this defect which was already detected previously.

3.Fixed:-When you find a bug and  do the necessary  changes.

4.Closed:-When the changes are made to the application such that the same bug does not appear again then the bug is said to be closed.

Note: Inbetween fixed and closed you may reject adefect then the bug is said to be rejected

Indra Jagatheesan

• Oct 4th, 2005

 

The bug life cycle are as follows:UNCONFIRMED This bug has recently been added to the database. Nobody has validated that this bug is true. Users who have the "can confirm" permission set may confirm this bug, changing its state to NEW. Or, it may be directly resolved and marked RESOLVED. NEW This bug has recently been added to the assignee's list of bugs and must be processed. Bugs in this state may be accepted, and become ASSIGNED, passed on to someone else, and remain NEW, or resolved and marked RESOLVED. ASSIGNED This bug is not yet resolved, but is assigned to the proper person. From here bugs can be given to another person and become NEW, or resolved and become RESOLVED. REOPENED This bug was once resolved, but the resolution was deemed incorrect. For example, a WORKSFORME bug is REOPENED when more information shows up and the bug is now reproducible. From here bugs are either marked ASSIGNED or RESOLVED. RESOLVED A resolution has been taken, and it is awaiting verification by QA. From here bugs are either re-opened and become REOPENED, are marked VERIFIED, or are closed for good and marked CLOSED. VERIFIED QA has looked at the bug and the resolution and agrees that the appropriate resolution has been taken. Bugs remain in this state until the product they were reported against actually ships, at which point they become CLOSED. CLOSED The bug is considered dead, the resolution is correct. Any zombie bugs who choose to walk the earth again must do so by becoming REOPENED.

santhosh

• Oct 7th, 2005

 

Once the test case for a particular functionality is executed and if any mis match with the SRS a tester raises a bug and itsstatus will be open,and if u use a automated tool for tracking,asandwen u log the bug,the default asignee i.e the developer will be loaded there,else your TL will be assigning them to developers, as a tester u cant assign directly to developers,then the bug status will be ASSIGNED.,they will be fixing the bug and its status will be FIXED andsend to us again,we will be retesting it again and if meets the spec, its status will be CLOSED,else it will be RE OPEN.

Vijayanand

• Oct 10th, 2005

 

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/Error Life Cycle’.New: When a bug is found/revealed for the first time, the software tester communicates it to his/her team leader (Test Leader) in order to confirm if that is a valid bug. After getting confirmation from the Test Lead, the software tester logs the bug and the status of ‘New’ is assigned to the bug. Assigned: After the bug is reported as ‘New’, it comes to the Development Team. The development team verifies if the bug is valid. If the bug is valid, development leader assigns it to a developer to fix it and a status of ‘Assigned’ is assigned to it. Open: Once the developer starts working on the bug, he/she changes the status of the bug to ‘Open’ to indicate that he/she is working on it to find a solution. Fixed: Once the developer makes necessary changes in the code and verifies the code, he/she marks the bug as ‘Fixed’ and passes it over to the Development Lead in order to pass it to the Testing team. Pending Retest: After the bug is fixed, it is passed back to the testing team to be retested and the status of ‘Pending Retest’ is assigned to it. Retest: The testing team leader changes the status of the bug, which is previously marked with ‘Pending Retest’ to ‘Retest’ and assigns it to a tester for retesting. Closed: After the bug is assigned a status of ‘Retest’, it is again tested. If the problem is solved, the tester closes it and marks it with ‘Closed’ status. Reopen: If after retesting the software for the bug opened, if the system behaves in the same way or same bug arises once again, then the tester reopens the bug and again sends it back to the developer marking its status as ‘Reopen’. Pending Rejected: If the developers think that a particular behavior of the system, which the tester reports as a bug has to be same and the bug is invalid, in that case, the bug is rejected and marked as ‘Pending Reject’. Rejected: If the Testing Leader finds that the system is working according to the specifications or the bug is invalid as per the explanation from the development, he/she rejects the bug and marks its status as ‘Rejected’. Postponed: Sometimes, testing of a particular bug has to be postponed for an indefinite period. This situation may occur because of many reasons, such as unavailability of Test data, unavailability of particular functionality etc. That time, the bug is marked with ‘Postponed’ status. Deferred: In some cases a particular bug stands no importance and is needed to be/can be avoided, that time it is marked with ‘Deferred’ status.

Vijay_anandd

 Profile Answers by Vijay_anandd 

• Oct 10th, 2005

 

Explain the Bug 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/Error Life Cycle’.New: When a bug is found/revealed for the first time, the software tester communicates it to his/her team leader (Test Leader) in order to confirm if that is a valid bug. After getting confirmation from the Test Lead, the software tester logs the bug and the status of ‘New’ is assigned to the bug. Assigned: After the bug is reported as ‘New’, it comes to the Development Team. The development team verifies if the bug is valid. If the bug is valid, development leader assigns it to a developer to fix it and a status of ‘Assigned’ is assigned to it. Open: Once the developer starts working on the bug, he/she changes the status of the bug to ‘Open’ to indicate that he/she is working on it to find a solution. Fixed: Once the developer makes necessary changes in the code and verifies the code, he/she marks the bug as ‘Fixed’ and passes it over to the Development Lead in order to pass it to the Testing team. Pending Retest: After the bug is fixed, it is passed back to the testing team to be retested and the status of ‘Pending Retest’ is assigned to it. Retest: The testing team leader changes the status of the bug, which is previously marked with ‘Pending Retest’ to ‘Retest’ and assigns it to a tester for retesting. Closed: After the bug is assigned a status of ‘Retest’, it is again tested. If the problem is solved, the tester closes it and marks it with ‘Closed’ status. Reopen: If after retesting the software for the bug opened, if the system behaves in the same way or same bug arises once again, then the tester reopens the bug and again sends it back to the developer marking its status as ‘Reopen’. Pending Rejected: If the developers think that a particular behavior of the system, which the tester reports as a bug has to be same and the bug is invalid, in that case, the bug is rejected and marked as ‘Pending Reject’. Rejected: If the Testing Leader finds that the system is working according to the specifications or the bug is invalid as per the explanation from the development, he/she rejects the bug and marks its status as ‘Rejected’. Postponed: Sometimes, testing of a particular bug has to be postponed for an indefinite period. This situation may occur because of many reasons, such as unavailability of Test data, unavailability of particular functionality etc. That time, the bug is marked with ‘Postponed’ status. Deferred: In some cases a particular bug stands no importance and is needed to be/can be avoided, that time it is marked with ‘Deferred’ status.

Vijay_anandd

 Profile Answers by Vijay_anandd 

• Oct 10th, 2005

 

Explain the Bug 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/Error Life Cycle’.New: When a bug is found/revealed for the first time, the software tester communicates it to his/her team leader (Test Leader) in order to confirm if that is a valid bug. After getting confirmation from the Test Lead, the software tester logs the bug and the status of ‘New’ is assigned to the bug. Assigned: After the bug is reported as ‘New’, it comes to the Development Team. The development team verifies if the bug is valid. If the bug is valid, development leader assigns it to a developer to fix it and a status of ‘Assigned’ is assigned to it. Open: Once the developer starts working on the bug, he/she changes the status of the bug to ‘Open’ to indicate that he/she is working on it to find a solution. Fixed: Once the developer makes necessary changes in the code and verifies the code, he/she marks the bug as ‘Fixed’ and passes it over to the Development Lead in order to pass it to the Testing team. Pending Retest: After the bug is fixed, it is passed back to the testing team to be retested and the status of ‘Pending Retest’ is assigned to it. Retest: The testing team leader changes the status of the bug, which is previously marked with ‘Pending Retest’ to ‘Retest’ and assigns it to a tester for retesting. Closed: After the bug is assigned a status of ‘Retest’, it is again tested. If the problem is solved, the tester closes it and marks it with ‘Closed’ status. Reopen: If after retesting the software for the bug opened, if the system behaves in the same way or same bug arises once again, then the tester reopens the bug and again sends it back to the developer marking its status as ‘Reopen’. Pending Rejected: If the developers think that a particular behavior of the system, which the tester reports as a bug has to be same and the bug is invalid, in that case, the bug is rejected and marked as ‘Pending Reject’. Rejected: If the Testing Leader finds that the system is working according to the specifications or the bug is invalid as per the explanation from the development, he/she rejects the bug and marks its status as ‘Rejected’. Postponed: Sometimes, testing of a particular bug has to be postponed for an indefinite period. This situation may occur because of many reasons, such as unavailability of Test data, unavailability of particular functionality etc. That time, the bug is marked with ‘Postponed’ status. Deferred: In some cases a particular bug stands no importance and is needed to be/can be avoided, that time it is marked with ‘Deferred’ status.

xxy

• Oct 19th, 2005

 

BUg life cycle:

Finding a bug......> Repoting a bug.....> Fixing the bug.......> Regretion testing

Anilkumar 9841237038

• Oct 20th, 2005

 

Detect defect----reproduce defect----report defect-----Resolve defect (nothing but fixing of defect by dev) ------Regression then Close

Anilkumar 9841237038

• Oct 20th, 2005

 

anu Wrote: This is not the correct ans for this qs. This ans should say if u asked stages of bug.

The bug cycle consists of 4 main stages those are:

1.New:- When you find a new bug in the application which was not detected previously.

2.Open:-Open this defect which was already detected previously.

3.Fixed:-When you find a bug and? do the necessary ?changes.

4.Closed:-When the changes are made to the application such that the same bug does not appear again then the bug is said to be closed.

Note: Inbetween fixed and closed you may reject adefect then the bug is said to be rejected

sreelatha

• Oct 22nd, 2005

 

Defect Detection

Defect Reproducing

Defect Reporting

Bug fixing

Bug Resolving

Bug Closing

vikramraj

• Oct 24th, 2005

 

Bug Life cycle

1. Creation of Bug

2. Assignment of Bug

3. Evaluation of Bug

4. Fixing of bug

5. Verification

Ranjeet Mishra

• Oct 25th, 2005

 

The Bug Cycle is basically the whole process when a bug found :-

1. Tester found a bug and raises that bug into bug tracking tool

2. Assign the bug to the TL or Concern Developer (As per Company Process)

3. Developer Resolve the Issue with some comments and Re-assign to the Tester.

4. Tester Verify the Issue, If it is resolved then close the issue

5. If the issue is not resolved then, again step 2,3,4 get repeated.

Thanks,

Ranjeet

SohanKarim

 Profile Answers by SohanKarim 

• Oct 25th, 2005

 

The typical lifecycle of a bug is as follows:1. Bug is identified in system and created in Bugs Online 2. Bug is assigned to a developer 3. Developer resolves bug or clarifies with user 4. Developer sets bug to "Completed" status and assigns back to original user 5. Original user verifies that bug has been resolved and if so sets bug to "Closed" status. If the bug was not resolved to the user's satisfaction they may assign it back to the developer with a description (by adding a new detail). If this occurs then the bug returns to step 2 above. Note: Bug life cycle can be differeent or customized with business needs and QA methodology

veenadevi

• Oct 26th, 2005

 

bug life cycle

1.open

2.assign

3.resolve

4re-open/close

Bhavana

• Oct 27th, 2005

 

1. new bug

2.open

3. work-in progress

4. fixed

5. retest

6.reopen(if test failed again)

7.closed

8.Deffered

hemanth

• Oct 28th, 2005

 

testing the application,detect defect,reproduce defect,report defect to developer,bug fixing,bug resolving,bug closeing.

vijayalaxmi

 Profile Answers by vijayalaxmi 

• Oct 31st, 2005

 

Bug Life Cycle:

Bug Life Cycle consists of-

Bug Open-

Open- Testers finds and logs bug.

Resolved-Programmer fixes the bug.

Closed-Tester confirms bug is fixed. 

mahesh

• Nov 2nd, 2005

 

NEW->open->fixed->ready to test->Close

satish`

• Nov 7th, 2005

 

Bug life Cycle is nothing but,

1.New

2. Open

3.Fixed

4.Closed

5.Reopen

rchiranjeevi

 Profile Answers by rchiranjeevi 

• Nov 9th, 2005

 

Bug life cycle consists of finding bug,reporting bug,bug fixing,regression testing to ensure bug fix work and finally closing bug.

srujan

 Profile Answers by srujan 

• Nov 11th, 2005

 

Hi, this is srujan..

Bug Life Cycle.

                      1.Defect detection

                      2.Defect Reproducible

                      3.Defect Reporting.

                      4.Bug Fixing.

                      5.Bug resolving.

                      6.Bug Closing.  

LeninAkhila

 Profile Answers by LeninAkhila 

• Nov 14th, 2005

 

                       

                         Testing a script                          

      If bug found                                     If no bugs found

      1.Goes to developer                         1.Sent to product release. 

      2.The bug is fixed                      

      3.Sent to the tester

      4.Tested again

Amit Pandey

• Nov 15th, 2005

 

Pls find below the bug life cycle-

               Detect Defect-Reproduce Defect-Report defect-Buge Fixed-Bug resolved.

raghava

• Nov 17th, 2005

 

hi,

bug lifecycle follows following process

1.new,2.open,3.assign,test,verified,deferred,reopened,duplicate,rejected,closed

parvathi

• Nov 18th, 2005

 

detect defect-->Report defect-->Fix Bug-->

Resolved Bug-->Close Bug.

madhumitta1

 Profile Answers by madhumitta1 

• Nov 21st, 2005

 

Bug life cycle:1.Bug creation,2.Bug Assignment,3.Bug Evaluation,4.Bug Fixing,5.Bug Verification.

choudary

• Nov 28th, 2005

 

Bug Life cycle consists of different phases. Generally a bug is raised due to 3 reasons. 1) when expected is not equal to actual. 2) when the functionality is not met. and 3)

The life cycle of the bug is as follows:

Detect the defect------Reproduce the defect-------Report the defect------Fixing the Defect-------Resolving the Defect--------Closing the Defect.

Detect the Defect: This the stage we face after executing the test scripts. During testing we get defects.

Reproduce the Defect: After detecting the Defect we have to reproduce the defect, because few defects amy not be reproducable. so we have to confirm our raised defect.If the defect is not reproducable all the iterations we perfom but occurs few times we have to get a screen print of that bug, so that a tester can have a proof of the bug raised.

Report the Defect: Once the defect is confirmed then the defect can be reported to the higher officials with the NEW status. (Test Team Lead).

Fixing the Defect: Once the defect is reported to the higher officials, then they verify the defect and if they find the defect to be valid then they change the status to OPEN and reports it to the development team.

Resolving the Defect: When the defect with status OPEN is sent to the development team, the first thing the developer does id verify if the defect is valid. He can either fix the defect if the defect is valid nor he can reject the defect if its invalid defect nor he may put a query to the tester saying that he needs more information regarding the defect.Once the defect is resolved, then the developer changes the defect status to FIXED and send it to the tester in the immediate build.

Closing the Defect: Then the tester again tests the defects and changes the status to CLOSED if the defect is resolved or change the status to REOPEN if the defect is not resloved at the tester environment. and send it back to the developer.

we have differnet status for a bug: 1) NEW, 2) OPEN, 3) FIXED, 4) CLOSED and 5) RE-OPEN. 

venkat

• Dec 21st, 2005

 

I would like to add "Verified" in between "fixed" and "Closed".One more thing is those states are user definable and depends on PM and QL.

schittoor

 Profile Answers by schittoor Questions by schittoor

• Apr 18th, 2006

 

bug creation

bug avalution

bug assignment

bug fixing

bug verification

This is the bug life cycle

Thanks

Srinivasulu.chittoor

Covansys Ind Pvt ltd