Scribd Logo
Upload

Welcome to Scribd!

  • Desfect Life Cycle

    Uploaded by

    ookhrd
    4 views2 pages
    A defect life cycle describes the stages a bug passes through from initial reporting to final resolution. It starts as new when first filed by QA, then moves to need more information if the developer requires clarification, or is rejected if found to not be a bug. Once fixed by a developer, it moves to resolved/fixed and then back to QA testing before being closed if verified as solved, or reopened if still occurring.

    Original Description:

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    A defect life cycle describes the stages a bug passes through from initial reporting to final resolution. It starts as new when first filed by QA, then moves to need more information if the developer requires clarification, or is rejected if found to not be a bug. Once fixed by a developer, it moves to resolved/fixed and then back to QA testing before being closed if verified as solved, or reopened if still occurring.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPTX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pptx, pdf, or txt
    4 views2 pages

    Desfect Life Cycle

    Uploaded by

    ookhrd
    A defect life cycle describes the stages a bug passes through from initial reporting to final resolution. It starts as new when first filed by QA, then moves to need more information if the developer requires clarification, or is rejected if found to not be a bug. Once fixed by a developer, it moves to resolved/fixed and then back to QA testing before being closed if verified as solved, or reopened if still occurring.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPTX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pptx, pdf, or txt
    of 2

    Defect life cycle

    New: When QA files new bug.

    Need more information: If developer is not clear


    about the bug reproduce steps provided by QA to
    reproduce the bug, then he/she can mark it as
    “need more information’

    Rejected/Invalid: Some times developer or team


    lead can mark the bug as Rejected or invalid if the
    system is working according to specifications and
    bug is just due to some misinterpretation.
    Defect life cycle
    Resolved/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.

    Reopen: If QA is not satisfy with the fix and if bug is


    still reproducible even after fix then QA can mark it as
    ‘Reopen’ so that developer can take appropriate action

    Closed: If bug is verified by the QA team and if


    the fix is ok and problem is solved then QA can
    mark bug as ‘Closed’.

    You might also like