Scribd Logo
Upload

Welcome to Scribd!

  • 96 views

    Defect Reporting

    Uploaded by

    Rajan Singh
    The document discusses defect management processes, including defining terms like bugs and errors, describing the different phases of the software development lifecycle where defects may occur. It provides details on defect reporting templates, processes, priorities, severities and status updates. Sample templates are given for defect reports, as well as examples of common defect life cycles that may occur from the initial reporting of a defect through fixing and closing.

    Copyright:

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

    Defect Reporting

    Uploaded by

    Rajan Singh
    96 views6 pages
    The document discusses defect management processes, including defining terms like bugs and errors, describing the different phases of the software development lifecycle where defects may occur. It provides details on defect reporting templates, processes, priorities, severities and status updates. Sample templates are given for defect reports, as well as examples of common defect life cycles that may occur from the initial reporting of a defect through fixing and closing.

    Original Description:

    Defect Reporting

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses defect management processes, including defining terms like bugs and errors, describing the different phases of the software development lifecycle where defects may occur. It provides details on defect reporting templates, processes, priorities, severities and status updates. Sample templates are given for defect reports, as well as examples of common defect life cycles that may occur from the initial reporting of a defect through fixing and closing.

    Copyright:

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

    Defect Reporting

    Uploaded by

    Rajan Singh
    The document discusses defect management processes, including defining terms like bugs and errors, describing the different phases of the software development lifecycle where defects may occur. It provides details on defect reporting templates, processes, priorities, severities and status updates. Sample templates are given for defect reports, as well as examples of common defect life cycles that may occur from the initial reporting of a defect through fixing and closing.

    Copyright:

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

    Defect Reporting

    9:28 PM G.C. REDDY NO COMMENTS

    Defect Management
    Terms:
    Application Life Cycle (ALM)
    Development Phase Testing Phase
    Production Phase
    -----------------------------------------------------------------Error
    Defect
    Failure
    Mistake

    Bug
    Fault

    -------------------------------------------------------------We have 3 phases in Software Application Life Cycle


    a) Development Phase
    In this phase If developers find any mismatch, they call it as Error or Mistake.
    b) Testing Phase
    In this phase If Testers find any mismatch, they call it as Defect or Bug or Fault.

    c) Production Phase
    In this phase If End users find any mismatch, they call it as Failure.
    Note: Terminology vary from one phase to another.
    ------------------------------------------------------------------

    Defect Management:
    Defect Reporting, Defect Tracking, and Status Tracking is called Defect Management.
    Some companies use Manual Process (Excel workbook), and some companies use Tool
    based process for Defect Management.
    Tools Examples:
    Bugzilla / Issue-Tracker / PR-Tracker etc...

    Jira, QC

    ---------------------------------------------------------------------

    Model Defect Report Template:


    ---------------------i) Defect Id: any unique name for Identifying the Defect (Alfa numeric)
    ii) Defect Description: Details about the Defect
    iii) Test Case Id: Corresponding Test Case Id for tracking
    iv) Tester: Tester's name (who found the Defect)
    v) Product Version: Version of the Product on which defect was found
    vi) Build Version: Version of the Build on which defect was found
    vii) Priority: Importance of the Defect based on Business /Customer
    viii) Severity: Importance of the Defect based on Functionality
    ix) Status: Status of Defect
    x) Reproducible or not: Yes / No
    If Reproducible:
    Steps:
    If not Reproducible:
    Attachments
    xi) Reporting to: Corresponding Developer
    xii) Remarks : Comments (Optional)
    ------------------------------------------------------

    Status: Status of Defect


    New: Tester provides new status while Reporting (for the first time)
    Open: Developer / Dev lead /DTT opens the Defect

    Rejected: Developer / Dev lead /DTT rejects if the defect is invalid or defect is duplicate.
    Fixed: Developer provides fixed status after fixing the defect
    Deferred: Developer provides this status due to time etc...
    Closed: Tester provides closed status after performing confirmation Testing
    Re-open: Tester Re-opens the defect with valid reasons and proofs
    -----------------------------------------------------------------Note: Defect Reporting Template vary from one company to another
    If we use Tool for Defect management, every tool provides their own template.

    Defect Reporting Process


    -----------------------Defect Reporting Process vary from one company to another.
    a)

    Small scale Company

    Tester -> Developer


    b) Medium

    scale Company

    Tester -> Test Lead -> Development Lead -> Developer


    c) Large

    scale Company

    Tester -> Test Lead -> DTT -> Development Lead -> Developer

    A Sample Defect Report


    --------------------i) Defect Id: FR_Usr_Df001
    ii) Defect Description: Agent Name accepting Numeric values
    iii) Test Case Id: FR_Usr_Tc-004
    iv) Tester: Kanaka Rao
    v) Product Version: 1.0

    vi) Build Version: 1.0


    vii) Priority: Medium
    viii) Severity: High
    ix) Status: New
    x) Reproducible or not: Yes
    Steps:
    1) Launch the Application
    2) Enter Numeric values into Agent Name field
    3) Enter valid Password
    4) Click on default(OK) button
    xi) Reporting to: xyz
    xii) Remarks : Comments (Optional)
    ----------------------------------Severity:
    Severity Levels depends on Company strategy
    a) 5 Level Severity
    Urgent
    Very High
    High
    Medium
    Low
    ----------a) 3 Level Severity
    High
    Medium

    Low
    ---------------------------------------------Priority

    Priority Levels depends on Company strategy

    a) 5 Level Priority
    Urgent
    Very High
    High
    Medium
    Low
    ----------a) 3 Level Priority
    High
    Medium
    Low
    ------------------------------------------------

    Defect Life Cycle


    -----------------Different Flows of the Defect
    a) New -> Opened -> Fixed -> Closed
    b) New -> Opened -> Rejected -> Closed
    c) New -> Opened -> Fixed -> Re-opened -> Fixed -> Closed
    d) New -> Opened -> Deferred
    e) New -> Opened -> Rejected -> Re-opened -> Fixed -> Closed
    Etc...
    ------------------------------------------------------------------------

    Also Visit:
    ---------------

    You might also like