[ Home  |  FAQ-Related Q&As  |  General Q&As  |  Answered Questions ]

    Search the Q&A Archives

...defect life cycle?

<< Back to: comp.software.testing Frequently Asked Questions (FAQ)

Question by jigarkumar
Submitted on 6/9/2004
Related FAQ: comp.software.testing Frequently Asked Questions (FAQ)
Rating: Rate this question: Vote
what is defect life cycle?


Answer by venkat
Submitted on 6/11/2004
Rating:  Rate this answer: Vote
fish model

 

Answer by MADHUSUDHAN REDDY
Submitted on 8/28/2004
Rating: Not yet rated Rate this answer: Vote
1.Testers will  identify the bug , then make the bug status to Open and send to developer
2.Developers fix it and change the status to reopen
3.Testing team again test it ,if bug found again change the status to Reopen and send back to developer else change the status to close.
  
Diff status are:
  open  -  resolve  - reopen - close


 

Answer by nammu
Submitted on 10/26/2004
Rating: Not yet rated Rate this answer: Vote
New
Open
Assigned
Fixed
Verified
Deferred
Pend
NoSim(Unable to simulate)
NAD(not a defect)
closed

 

Answer by sangi
Submitted on 3/4/2005
Rating: Not yet rated Rate this answer: Vote
Defect life cycle starts when a defect is found and ends when it is fixed or no longer in use.
when a defect is found it needs to be routed to a correct person like developer.defect report include status,priority,severity,date created,In which Test case it was found.
Developer after seeing this fixed, change the status "open" which means they r working on that.After fixing the defect they change status "fixed" and send to testers
Testers retest the fixes ,if found satisfied can close the defect or reopen the defect and roll back to developers

 

Answer by vishali
Submitted on 4/26/2005
Rating: Not yet rated Rate this answer: Vote
The defect life cycle is:
first when the defect is found it is made note of. (this is called the New stage)
Then it is sent to the developer (this is called the Open stage)
Once the developer fixes and sends back to the tester (it is called as Fixed)
Now the tester checks if the bug had been fixed , if it is fixed (it is called Closed)

if the bug is not fixed it is returned back to the developer (this is called as Reopen)

 

Answer by Shivamshu Ati
Submitted on 4/27/2005
Rating: Not yet rated Rate this answer: Vote
A bug life cycle starts from the moment it is discovered...let me put it in steps
1.Discover/Uncover a bug
2.Report the bug with status as open

3.From here it can be marked as Not a bug, Reject, Fixed.

3.1 If status is Not a bug it can be closed with valid arguments supporting the status

3.2 If it is Rejected ..same as not a bug

3.3 If it is fixed....verify the fix and mark the status as...
4.Verified and closed (if you think it is fixed)

5.Reopen if the bug still exist (if the iteration to recreate the same bug changes a bit then too simply reopen it with further comments)
6.Similar cycle continues till the bug is finally marked as verified and closed.

 

Answer by anees
Submitted on 6/29/2005
Rating: Not yet rated Rate this answer: Vote
defect life cycle is the process in which the status of the defect comes in to picture i.e whether it is opened,closed or canceled

 

Answer by yashu
Submitted on 9/26/2005
Rating: Not yet rated Rate this answer: Vote
defect life cycle gives different stages of the defect




 

Answer by sun
Submitted on 10/18/2005
Rating: Not yet rated Rate this answer: Vote
Defect life cycle is the state of defect ,in which the developer know from defect life cycle that bug is open, reopen or closed.In defect life cycle there are there state1.Pending 2) Withdrawn 3) Redundent

 

Answer by venkat
Submitted on 11/10/2005
Rating: Not yet rated Rate this answer: Vote
Defect Detection -> Defect Reproducing -> Defect Submitting -> Defect finding -> Defect Resolving -> Defect Closing Review

 

Answer by Piyush Sharma
Submitted on 11/24/2005
Rating: Not yet rated Rate this answer: Vote
Following are states in bug's Life
1. Just created - New/Open
2. Fixed by Developer - Fixed
3. Verified by QA and Failed - Verified Failed
4. Verified by QA and Passed - Verified Closed
5. If it was not a bug then status can be - Closed
6. If defect is resurfaces after closing then status become - Re-Opened


 

Answer by dee
Submitted on 12/15/2005
Rating: Not yet rated Rate this answer: Vote
Defect cycle which involves:

Defect->Logged -> Open -> Assign to dev -> (->Fixed or Deferred or Enhancement or Duplicate or Not reproducible or Fix in next release or Fix in SP1/SP2 ->) -> Assigned back to you -> Close.

 

Answer by sai
Submitted on 12/21/2005
Rating: Not yet rated Rate this answer: Vote

this is from buzzle.com...
What is a 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’.

(Right from the first time any bug is detected till the point when the bug is fixed and closed, it is assigned various statuses which are New, Open, Postpone, Pending Retest, Retest, Pending Reject, Reject, Deferred, and Closed. For more information about various statuses used for a bug during a bug life cycle, you can refer to article ‘Software Testing – Bug & Statuses Used During A Bug Life Cycle’)

There are seven different life cycles that a bug can passes through:

< I > Cycle I:
1) A tester finds a bug and reports it to Test Lead.
2) The Test lead verifies if the bug is valid or not.
3) Test lead finds that the bug is not valid and the bug is ‘Rejected’.

< II > Cycle II:
1) A tester finds a bug and reports it to Test Lead.
2) The Test lead verifies if the bug is valid or not.
3) The bug is verified and reported to development team with status as ‘New’.
4) The development leader and team verify if it is a valid bug. The bug is invalid and is marked with a status of ‘Pending Reject’ before passing it back to the testing team.
5) After getting a satisfactory reply from the development side, the test leader marks the bug as ‘Rejected’.

< III > Cycle III:
1) A tester finds a bug and reports it to Test Lead.
2) The Test lead verifies if the bug is valid or not.
3) The bug is verified and reported to development team with status as ‘New’.
4) The development leader and team verify if it is a valid bug. The bug is valid and the development leader assigns a developer to it marking the status as ‘Assigned’.
5) The developer solves the problem and marks the bug as ‘Fixed’ and passes it back to the Development leader.
6) The development leader changes the status of the bug to ‘Pending Retest’ and passes on to the testing team for retest.
7) The test leader changes the status of the bug to ‘Retest’ and passes it to a tester for retest.
8) The tester retests the bug and it is working fine, so the tester closes the bug and marks it as ‘Closed’.

< IV > Cycle IV:
1) A tester finds a bug and reports it to Test Lead.
2) The Test lead verifies if the bug is valid or not.
3) The bug is verified and reported to development team with status as ‘New’.
4) The development leader and team verify if it is a valid bug. The bug is valid and the development leader assigns a developer to it marking the status as ‘Assigned’.
5) The developer solves the problem and marks the bug as ‘Fixed’ and passes it back to the Development leader.
6) The development leader changes the status of the bug to ‘Pending Retest’ and passes on to the testing team for retest.
7) The test leader changes the status of the bug to ‘Retest’ and passes it to a tester for retest.
8) The tester retests the bug and the same problem persists, so the tester after confirmation from test leader reopens the bug and marks it with ‘Reopen’ status. And the bug is passed back to the development team for fixing.

< V > Cycle V:
1) A tester finds a bug and reports it to Test Lead.
2) The Test lead verifies if the bug is valid or not.
3) The bug is verified and reported to development team with status as ‘New’.
4) The developer tries to verify if the bug is valid but fails in replicate the same scenario as was at the time of testing, but fails in that and asks for help from testing team.
5) The tester also fails to re-generate the scenario in which the bug was found. And developer rejects the bug marking it ‘Rejected’.

< VI > Cycle VI:
1) After confirmation that the data is unavailable or certain functionality is unavailable, the solution and retest of the bug is postponed for indefinite time and it is marked as ‘Postponed’.

< VII > Cycle VII:
1) If the bug does not stand importance and can be/needed to be postponed, then it is given a status as ‘Deferred’.

This way, any bug that is found ends up with a status of Closed, Rejected, Deferred or Postponed.




 

Answer by Raghavendra Rao
Submitted on 3/9/2006
Rating: Not yet rated Rate this answer: Vote
From the new status of the defect to the closed state.



 

Answer by Prasad
Submitted on 3/16/2006
Rating: Not yet rated Rate this answer: Vote
Starting from Submitting the bug or defect it undergoes several states before it gets CLOSED
1)Assigned
2)Opened
3)Resolved/Rejected

 

Answer by Goldie
Submitted on 9/15/2006
Rating: Not yet rated Rate this answer: Vote
new -open - it can be rejected/incomplete/or

withdrawn if the review board decides-closed-

fixed

 

Answer by Deepak
Submitted on 11/20/2006
Rating: Not yet rated Rate this answer: Vote
Defect life cycle defines the various stages of a defect found and raised during a software testing process.

 

Answer by raj
Submitted on 1/16/2007
Rating: Not yet rated Rate this answer: Vote
defect life cycle means  the cycle which takes place when the bugs are found and  are made to recorrect or send to the developers for the correction, later again the changes are tested and confirms that there are no bugs the testing is closed.

 

Answer by anildas
Submitted on 4/18/2007
Rating: Not yet rated Rate this answer: Vote
Defect Life Cycle is nothing but the various phases a Bug undergoes after it is raised or reported.

    * New or Opened
    * Assigned
    * Fixed
    * Re-open
    * Closed
    * Rejected

 

Answer by Uzair
Submitted on 4/26/2007
Rating: Not yet rated Rate this answer: Vote
Defect life cycle encompasses following steps.
        „³ Detect defect
        „³ Reproduce defect
        „³ Report defect
        „³ Verify defect (If rejected it is cancelled and process stops here, other wise following steps are included.
        „³ Assign Defect
        „³ Defect Fixing
        „³ Defect closing
        „³ Defect Resolution Verification.
Defect verification (in case of conflict between developer and Tester)is done by manager). Defect fixing and defect closing is performed by the developer.

 

Answer by yubaraj
Submitted on 5/8/2007
Rating: Not yet rated Rate this answer: Vote
Defect life cycle start form open -open- fixed -reopen -closed

 

Answer by ABTester
Submitted on 6/7/2007
Rating: Not yet rated Rate this answer: Vote
hello Jigar,

i my company we are using this life cycle for the defect -
Defect Found -> Defect Logged -> Defect Debugged -> Defect Reassigned -> Defect Rechecked -> Defect Closed(If Fixed)
  or |
(If Bug Founded again)Defect Reopened -> Defect Debugged -> Defect Reassigned -> Defect Rechecked -> Defect Closed

 

Answer by vartika
Submitted on 7/4/2007
Rating: Not yet rated Rate this answer: Vote
Defect Life Cycle
1.System Requirement
2.Test Plan
3.Test Case Design
4.Test case Execution
5.Preparing Defect Report
6.Defect Analysis
6.Retesting or Regression Testing
7. Support, Maintenance

 

Your answer will be published for anyone to see and rate.  Your answer will not be displayed immediately.  If you'd like to get expert points and benefit from positive ratings, please create a new account or login into an existing account below.


Your name or nickname:
If you'd like to create a new account or access your existing account, put in your password here:
Your answer:

FAQS.ORG reserves the right to edit your answer as to improve its clarity.  By submitting your answer you authorize FAQS.ORG to publish your answer on the WWW without any restrictions. You agree to hold harmless and indemnify FAQS.ORG against any claims, costs, or damages resulting from publishing your answer.

 

FAQS.ORG makes no guarantees as to the accuracy of the posts. Each post is the personal opinion of the poster. These posts are not intended to substitute for medical, tax, legal, investment, accounting, or other professional advice. FAQS.ORG does not endorse any opinion or any product or service mentioned mentioned in these posts.

 

<< Back to: comp.software.testing Frequently Asked Questions (FAQ)

[ Home  |  FAQ-Related Q&As  |  General Q&As  |  Answered Questions ]
© 2008 FAQS.ORG. All rights reserved.