SPONSORS:






User Tag List

Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Results 1 to 9 of 9

Thread: Bug Life Cycle

  1. #1
    Junior Member
    Join Date
    Nov 2010
    Posts
    6
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Bug Life Cycle

    Once Final Testing is done and then also If client or customer of that project finds error then what should be the next steps fore this founded bugs?



    Regards,
    Devendra Patel
    OnlineGCET.COM

  2. #2
    Moderator Joe Strazzere's Avatar
    Join Date
    May 2000
    Location
    USA
    Posts
    13,170
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    1 Thread(s)
    Total Downloaded
    0

    Re: Bug Life Cycle

    [ QUOTE ]
    If client or customer of that project finds error then what should be the next steps fore this founded bugs?

    [/ QUOTE ]

    Fix the bug.
    Verify the fix.
    Regression tests.
    Release to production.
    Joe Strazzere
    Visit my website: AllThingsQuality.com to learn more about quality, testing, and QA!

  3. #3
    Member
    Join Date
    Mar 2010
    Location
    Hyderabad, Andhra Pradesh, India
    Posts
    48
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Bug Life Cycle

    First Identify the severity of the Bug. If it is of high severity, then Fix the bug and test it in the same revision as it is there in the client's machine and also do the regression. Then ask the client to verify it and once it passes release it into production.

  4. #4
    Junior Member
    Join Date
    Nov 2010
    Posts
    3
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Bug Life Cycle

    In that case first of all we should try to reproduce the bug at our environment if that exists then we should know the root cause why its left and not reported from our end,
    It might be possible that issue will not get reproduced at our end then we will ask the client for reproducing scenario and then will check at client's environment or real time environment.

    After reproducing that particular bug, we should follow the same bug life cycle and will get the issue fixed ASAP.This is a situation that occurs many times during software testing life cycle.

  5. #5
    Apprentice
    Join Date
    May 2010
    Posts
    24
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Bug Life Cycle

    I would like to modify Joe's explanation & provide inputs in detail -

    First, try to reproduce in customer environment & in-house
    Next, look for an immediate workaround (if you can find 1) to help the customer save on time
    Research on the RCA
    Fix the bug.
    Verify the fix.
    Regression tests.
    Notify the Dev team to avoid such bugs in future releases
    Notify the QA team to include the missing testcases & identigy other regression areas
    Release to production.

  6. #6
    Moderator
    Join Date
    Mar 2004
    Location
    West Coast of the East Coast!
    Posts
    7,756
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Bug Life Cycle

    [ QUOTE ]
    Notify the Dev team to avoid such bugs in future releases


    [/ QUOTE ]

    RIGHT!..."Yeah, Hello Development, can you hear me? Please don't send us another bug like that last one or we'll have to send Quido over there to break some knee-caps. Got it Buddy? Yose better clean up your act".
    Personal Comment

    Success is the ability to go from one failure to another with no loss of enthusiasm.
    ~ Winston Churchill ~


    ...Rich Wagner

  7. #7
    Super Member FredMan's Avatar
    Join Date
    Oct 2007
    Location
    Lenexa, Kansas
    Posts
    1,218
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Bug Life Cycle

    Rich, you made my day. LMAO
    Onward thru the fog...

  8. #8
    Junior Member
    Join Date
    Jan 2011
    Posts
    1
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Bug Life Cycle

    1. New : when a bug is found out .
    2. Open : If the bug is genuine , it is opened.
    3. Assign : The bug is assigned to a developer to get it fixed.
    4. Reject/Defer : If the bug if found invalid it is rejected by the developer or can be deferred if the bug is to be fixed later.
    5. Test : The bug is fixed and is sent to the tester.
    6. Reopen : If the bug still exists , it is reopened and sent to the developer .
    7. Verify : The bug when fixed comes back for testing and if everything goes fine , it is verified .
    8. Close : The bug cycle is closed finally .

  9. #9
    Member
    Join Date
    Nov 2010
    Location
    London
    Posts
    70
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Bug Life Cycle

    [ QUOTE ]
    1. New : when a bug is found out .
    2. Open : If the bug is genuine , it is opened.
    3. Assign : The bug is assigned to a developer to get it fixed.
    4. Reject/Defer : If the bug if found invalid it is rejected by the developer or can be deferred if the bug is to be fixed later.
    5. Test : The bug is fixed and is sent to the tester.
    6. Reopen : If the bug still exists , it is reopened and sent to the developer .
    7. Verify : The bug when fixed comes back for testing and if everything goes fine , it is verified .
    8. Close : The bug cycle is closed finally .

    [/ QUOTE ]

    And if the developers don't do this - "Notify the Dev team to avoid such bugs in future releases"

    Then, welcome to the real world, you get to go through the complete loop loadsa times...joy
    Rob Broadhurst
    Passed the Microsoft Virtual Academy course on SQL Azure now doing the Windows Azure course.
    www.robertbroadhurst.com

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Search Engine Optimisation provided by DragonByte SEO v2.0.36 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Resources saved on this page: MySQL 7.89%
vBulletin Optimisation provided by vB Optimise v2.6.4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.2.8 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominate (Lite) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 10:00 AM.

Copyright BetaSoft Inc.