Data Migration Test Results Template

  • Published on
    28-Oct-2015

  • View
    180

  • Download
    0

DESCRIPTION

Data Migration Test Results Template

Transcript

<p>Test Results TEMPLATE</p> <p>Data Migration</p> <p>Project Identification </p> <p>Project NameCPI Project Number</p> <p>Customer NameCustomer Number</p> <p>SAP Project ManagerCustomer Project Manager</p> <p>Document Identification </p> <p>AuthorDocument Location (repository/path/name)</p> <p>Anthony Berland</p> <p> VersionStatusDate (YYYY-MM-DD)Document Classification</p> <p>0.1Draft2011-06-21Internal</p> <p>Revision history</p> <p> VersionDateDescription</p> <p>0.1June 21, 2011First draft of a template for data migration test results </p> <p>0.2</p> <p>Review and Approval</p> <p>NameKey Stakeholder</p> <p>Date (YYYY-MM-DD)</p> <p>NameKey Stakeholder</p> <p>Date (YYYY-MM-DD)</p> <p>TABLE OF CONTENT </p> <p>Purpose of the document3Intended Audience3Project Overview3Description3Organization and contact responsibilities3Related documents3Scope and limitations of testing3Test Report4Report Identification4Test Cases Summary Report4Defects Summary Report4Open issues5Appendix5</p> <p>Purpose of the documentThis document is to provide a deliverable that will report results of individual test cycles.Adapt the purpose regarding on the project.</p> <p>Intended AudienceList the categories of people the document is addressed to; no name lists should appear here.</p> <p>Project OverviewDescriptionOverall project description; a brief description may be enough here since a sub-section refers below to all the existing documents</p> <p>Organization and contact responsibilitiesOrganization and contact responsibilities; it is best practices to gather the name of all the people involved in the project, business or technical ones, in order to react quickly and to get fast answers to any questionNameRoleCompany</p> <p>e.g. John Doee.g. Project Managere.g. SAP</p> <p>Related documentsRelevant documents that can be useful for test reporting. A row for every identified document appears here, the location must be indicated, should be a link or a path (if no document applicable, delete the row or put N/A in the Location column).CategoryNameDescriptionLocation</p> <p>Data Quality PlanData Quality MetricsPresentation containing possible dashboards for tracking data migration quality</p> <p>Data Quality Strategy and DesignTemplate to capture the organization structure (people) and process required to capture and report data quality throughout the data migration effort.</p> <p>Testing StrategyTesting StrategyOutlines an overall test strategy for the data migration.</p> <p>Unit TestCaptures test plans by business object.</p> <p>Final Data Quality AssessmentFinal Data Quality AssessmentDocuments and reports assessment.</p> <p>Data Migration Test ResultsData Migration Test ResultsCaptures results of individual test cycles.Current Document</p> <p>Scope and limitations of testingObjectives of testing effort, testing priorities and focus. Relevant non scope areas must be reminded here.</p> <p>Test ReportThe test report shall contain tree sections: the header of the report, then the status of each trial run in terms of test cases, and finally the status of each trial run regarding on the number of defects (first an overview of the detected defects, then an overview of the defects that are still open).</p> <p>Report IdentificationThis sub section is aimed to present what has been tested and how. This is kind of a header for the report.IDCompleted byDateTesting nameTotal number of test cases</p> <p>report project identifiertester name who completed the reportdate of the reporttype of test (e.g. unit, integration, acceptance)total number of project test cases</p> <p>Test Cases Summary ReportThis sub section contains the status of the different trial runs regarding the test cases that were planned.Trial runTotal number of test cases% Started% Passed% Failed</p> <p>describe the test period (Week, Month) there is usually three trial runs number of test cases planned to be run during the periodtotal number of test cases started / total number of test casestotal number of test cases passed / total number of test casestotal number of test cases failed / total number of test cases</p> <p>Defects Summary ReportOverall status of the defects.</p> <p>Detected Defects Summary ReportThis report contains a row for each trial run and aims to sum up how many defects have been detected and their weight in terms of severity first, and priority then.Trail RunTotal DefectsTotal Closed Defects% High Severity% Medium Severity% Low Severity% High Priority% Medium Priority% Low Priority</p> <p>as abovenumber of non rejected defects detected within the whole testing project number of closed defectspercentage of the most critical defects, regarding the total defect numberpercentage of the mid critical defects, regarding the total defect numberpercentage of the least critical defects, regarding the total defect numberpercentage of the most urgent defects, regarding the total defect numberpercentage of the mid urgent defects, regarding the total defect numberpercentage of the least urgent defects, regarding the total defect number</p> <p>Open Defects Summary ReportThis report contains a row for each trial run and aims to sum up how many defects are still open and their weight in terms of severity first and then priority.Trail RunTotal Open Defects% High Severity% Medium Severity% Low Severity% High Priority% Medium Priority% Low Priority</p> <p>as abovenumber of defects still openpercentage of the most critical defects that are still openpercentage of the mid critical defects that are still openpercentage of the least critical defects that are still openpercentage of the most urgent defects that are still openpercentage of the mid urgent defects that are still openpercentage of the least urgent defects that are still open</p> <p>Open issuesIDDescriptionOwnerOpen dateDue date</p> <p>AppendixGlossary, acronyms, etc.</p> <p>Copyright/Trademark</p>

Recommended

View more >