Scribd Logo
Upload

Welcome to Scribd!

  • 41 views

    State of Michigan: (Insert System or Project Name Here) (Inset Phase or Product Increment)

    Uploaded by

    Sam
    This test closure report summarizes testing activities for a phase or product increment of a Michigan state system or project. Key information includes test metrics like the number of tests planned and executed, the pass rate, and defect analysis. The overall recommendation is to proceed to the next phase of testing based on the pass rate meeting the exit criteria, though some outstanding issues are documented. Approval from stakeholders is still needed before proceeding further.

    Copyright:

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

    State of Michigan: (Insert System or Project Name Here) (Inset Phase or Product Increment)

    Uploaded by

    Sam
    41 views5 pages
    This test closure report summarizes testing activities for a phase or product increment of a Michigan state system or project. Key information includes test metrics like the number of tests planned and executed, the pass rate, and defect analysis. The overall recommendation is to proceed to the next phase of testing based on the pass rate meeting the exit criteria, though some outstanding issues are documented. Approval from stakeholders is still needed before proceeding further.

    Original Description:

    sem format

    Original Title

    SEM-0607_557511_7_578596_7

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This test closure report summarizes testing activities for a phase or product increment of a Michigan state system or project. Key information includes test metrics like the number of tests planned and executed, the pass rate, and defect analysis. The overall recommendation is to proceed to the next phase of testing based on the pass rate meeting the exit criteria, though some outstanding issues are documented. Approval from stakeholders is still needed before proceeding further.

    Copyright:

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

    State of Michigan: (Insert System or Project Name Here) (Inset Phase or Product Increment)

    Uploaded by

    Sam
    This test closure report summarizes testing activities for a phase or product increment of a Michigan state system or project. Key information includes test metrics like the number of tests planned and executed, the pass rate, and defect analysis. The overall recommendation is to proceed to the next phase of testing based on the pass rate meeting the exit criteria, though some outstanding issues are documented. Approval from stakeholders is still needed before proceeding further.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    You are on page 1of 5

    State of Michigan

    (Insert System or Project Name Here)


    (Inset Phase or Product Increment)
    Test Closure Report

    1. General Information

    System or Project
    Creation Date:
    ID/Acronym:
    Client Agency: Modification Date:
    Author(s): DTMB Authorized by:

    2. Privacy Information
    This document may contain information of a sensitive nature. This information should not be given to
    persons other than those who are involved with this system/project or who will become involved during
    its lifecycle.

    3. Revision History
    The Project Manager will maintain this information and provide updates as required. All updates to the
    Project Management Plan and component plans should be documented in this section.
    Revision Date Author Section(s) Summary

    Test Closure Report 1 of 5 SEM-0607 (Rev. 07/2017)


    4. Overview
    This document is a summary of the results of the <Phase/Product Increment> Testing activities and is
    intended to assist stakeholders in making Stage Exit and (Go/No Go) decisions.
    The project’s Test Strategy document should be reviewed before completing this report. All metrics and
    defect reporting outlined in the Test Strategy must be reported in this document. At the Test Manager’s
    discretion, and in collaboration with Agency Partners, additional items may be added to those already
    defined. Wherever possible, create and attach reports from; the automated testing, change
    management, or backlog/test management tools for the reporting details.
    Whenever the words “test phase” are used within this document, this is in reference to either a specific
    test phase (waterfall) or for an occurrence of Deploy Product Increment (agile) testing.

    5. Summation and Recommendation


    In the space provided below, briefly describe the overall experience during this testing phase. This
    description should specifically express the recommendation (from the testing perspective) as to whether
    the project should proceed to the next phase of testing, move to the next product increment or be
    implemented as appropriate.

    5.1. Notable Events


    This section should include any specific events/circumstances that affected the execution of testing
    during this phase.

    5.2. Tests Executed


    Test Cycle Planned Number of Number of Passed Number of Test
    No. Number of Tests Passed Test Percentage Failed Test Failure
    Tests per Executed Cases Cases Rate per
    Test Cycle Cycle

    Success criteria for this phase of testing is a pass rate of <XX>. This test phase had a pass rate of <XX>
    which <meets/does not meet> the exit criteria for this phase of testing.
    Describe any exception or factors to the numbers supplied above:

    6. Defect Analysis
    Complete the table below listing the defect metric counts from this phase of testing. List any issues still
    outstanding at the end of this test phase.

    6.1. Defect Metrics


    Priority No. Defects No. Defects No. No. Defects No. Defects
    Opened Closed Defects On Rejected Open at end of

    Test Closure Report 2 of 5 SEM-0607 (Rev. 07/2017)


    Hold Test Phase
    Critical
    High
    Medium
    Low

    6.2. Outstanding Issues


    Defect ID Description Severity / Action Plan
    Impact

    7.

    Change Requests
    Attach a report of any change requests generated during the test phase or list them here.

    8. Exit Criteria Status


    The project will be adhering to the exit criteria listed here as the main criteria in the Go/No Go and
    Stage Exit decisions.
    Exit Criteria Criteria Met? If No, Describe Plan of Action
    (Yes/No)
    All test scripts have been successfully
    executed.
    All expected and actual results are captured
    and documented with the test script(s).
    All identified critical or high severity defects
    have been corrected and retested.
    Any unresolved defects are documented
    and signed-off by the project manager.
    Pass Rate is over <xx %>.
    <Other project Specific>

    9. Approvals
    Approvers Signatures (must be authorized approvers/members of the project Change Control Board).
    Role Name/Title Signature Date
    Business Owner
    (Authorized
    Approver)

    Test Closure Report 3 of 5 SEM-0607 (Rev. 07/2017)


    Role Name/Title Signature Date
    DTMB System
    Owner (if
    identified)
    Project Manager
    Project Test
    Manager

    Test Closure Report 4 of 5 SEM-0607 (Rev. 07/2017)


    Test Closure Report 5 of 5 SEM-0607 (Rev. 07/2017)

    You might also like