Scribd Logo
Upload

Welcome to Scribd!

  • 34 views

    What Is A Defect Life Cycle or A Bug Lifecycle in Software Testing?

    Uploaded by

    yamuna
    Defect life cycle refers to the stages a bug goes through from being discovered to being resolved. It starts when a bug is logged as new and ends when it is closed. The main stages are: 1) new, 2) assigned, 3) open, 4) fixed, 5) pending retest, 6) retest, 7) verified, 8) reopened, 9) closed, 10) duplicate, 11) rejected, 12) deferred, and 13) not a bug. The bug is passed between testers and developers through these stages until it is ultimately closed.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    What Is A Defect Life Cycle or A Bug Lifecycle in Software Testing?

    Uploaded by

    yamuna
    34 views2 pages
    Defect life cycle refers to the stages a bug goes through from being discovered to being resolved. It starts when a bug is logged as new and ends when it is closed. The main stages are: 1) new, 2) assigned, 3) open, 4) fixed, 5) pending retest, 6) retest, 7) verified, 8) reopened, 9) closed, 10) duplicate, 11) rejected, 12) deferred, and 13) not a bug. The bug is passed between testers and developers through these stages until it is ultimately closed.

    Original Description:

    good

    Original Title

    Next Topic

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Defect life cycle refers to the stages a bug goes through from being discovered to being resolved. It starts when a bug is logged as new and ends when it is closed. The main stages are: 1) new, 2) assigned, 3) open, 4) fixed, 5) pending retest, 6) retest, 7) verified, 8) reopened, 9) closed, 10) duplicate, 11) rejected, 12) deferred, and 13) not a bug. The bug is passed between testers and developers through these stages until it is ultimately closed.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    34 views2 pages

    What Is A Defect Life Cycle or A Bug Lifecycle in Software Testing?

    Uploaded by

    yamuna
    Defect life cycle refers to the stages a bug goes through from being discovered to being resolved. It starts when a bug is logged as new and ends when it is closed. The main stages are: 1) new, 2) assigned, 3) open, 4) fixed, 5) pending retest, 6) retest, 7) verified, 8) reopened, 9) closed, 10) duplicate, 11) rejected, 12) deferred, and 13) not a bug. The bug is passed between testers and developers through these stages until it is ultimately closed.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 2

    Next Topic

    Previous Topic

    What is a Defect Life Cycle or a Bug


    lifecycle in software testing?
    386

    76 75

    Defect life cycle is a cycle which a defect goes through during its lifetime. It starts when defect is found and ends when a defect is closed, after ensuring its not
    reproduced. Defect life cycle is related to the bug found during testing.

    The bug has different states in the Life Cycle. The Life cycle of the bug can be shown diagrammatically as follows:

    Bug or defectlife cycle includes following steps or status:

    1. New: When a defect is logged and posted for the first time. Its state is given as new.

    2. Assigned: After the tester has posted the bug, the lead of the tester approves that the bug is genuine and he assigns the bug to corresponding developer
    and the developer team. Its state given as assigned.

    3. Open: At this state the developer has started analyzing and working on the defect fix.
    4. 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. Pending retest: After fixing the defect the developer has given that particular code for retesting to the tester. Here the testing is pending on the testers
    end. Hence its status is pending retest.

    6. Retest: At this stage the tester do the retesting of the changed code which developer has given to him to check whether the defect got fixed or not.

    7. Verified: The tester tests the bug again after it got fixed by the developer. If the bug is not present in the software, he approves that the bug is fixed and
    changes the status to verified.

    8. Reopen: If the bug still exists even after the bug is fixed by the developer, the tester changes the status to reopened. The bug goes through the life
    cycle once again.

    9. Closed: Once the bug is fixed, it is tested by the tester. If the tester feels that the bug no longer exists in the software, he changes the status of the bug to
    closed. This state means that the bug is fixed, tested and approved.

    10. Duplicate: If the bug is repeated twice or the two bugs mention the same concept of the bug, then one bug status is changed to duplicate.

    11. Rejected: If the developer feels that the bug is not genuine, he rejects the bug. Then the state of the bug is changed to rejected.

    12. Deferred: The bug, changed to deferred state means the bug is expected to be fixed in next releases. The reasons for changing the bug to this state have
    many factors. Some of them are priority of the bug may be low, lack of time for the release or the bug may not have major effect on the software.

    13. Not a bug: The state given as Not a bug if there is no change in the functionality of the application. For an example: If customer asks for some change
    in the look and field of the application like change of colour of some text then it is not a bug but just some change in the looks of the application.

    You might also like

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy