Scribd Logo
Upload

Welcome to Scribd!

  • Bug Life Cycle

    Uploaded by

    בני קון
    9 views1 page
    The document outlines the typical lifecycle of a bug, including stages from initial proposal through resolution. Bugs start as proposed, then move to active once triaged and a developer is investigating. They become resolved once fixed or determined to be by design. From the resolved stage, bugs are then closed once validated or marked with a status like cannot reproduce, deferred, or duplicate.

    Original Description:

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document outlines the typical lifecycle of a bug, including stages from initial proposal through resolution. Bugs start as proposed, then move to active once triaged and a developer is investigating. They become resolved once fixed or determined to be by design. From the resolved stage, bugs are then closed once validated or marked with a status like cannot reproduce, deferred, or duplicate.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    9 views1 page

    Bug Life Cycle

    Uploaded by

    בני קון
    The document outlines the typical lifecycle of a bug, including stages from initial proposal through resolution. Bugs start as proposed, then move to active once triaged and a developer is investigating. They become resolved once fixed or determined to be by design. From the resolved stage, bugs are then closed once validated or marked with a status like cannot reproduce, deferred, or duplicate.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 1

    Bug life cycle

    Proposed – before bug triage\before developer started working on the item.

    Active- after bug triage, developer investigating and working on a fix

    Resolved – back to QA

     As designed: not a bug, that’s Is how the flow is design, if it’s not good we can create a
    feature to change it.
     Cannot reproduce: Monitor state, waiting for the bug to reproduce in order to grab the
    necessary information to fix it.
     Deferred: not going to be fixed any time soon, not using this one in general.
     Duplicate: already has a ticket in the TFS on the same issue.
     Fixed: most common, bug was fixed and ready for validation.

    Closed.

    You might also like