Test Results Template

INTERNAL
PROJECT IDENTIFICATION

Project Name CPI Project Number

<Project Name>
Customer Name Customer Number
<Customer Name>
SAP Project Manager Customer Project Manager
<SAP Project Manager> <Customer Project Manager>

DOCUMENT IDENTIFICATION

Author Document Location (repository/path/name)

Anthony Berland <Document location>
Version Status Date (YYYY-MM-DD) Document Classification
0.1 Draft <Date> Internal

REVISION HISTORY

Version Date Description

0.1 January 03, 2018

REVIEW AND APPROVAL

Name Date (YYYY-MM-DD)

Key Stakeholder

Name Date (YYYY-MM-DD)

Key Stakeholder

2
TABLE OF CONTENTS
PURPOSE OF THE DOCUMENT 4
INTENDED AUDIENCE4
PROJECT OVERVIEW 4
Description...................................................................................................................................................... 4
Organization and contact responsibilities................................................................................................... 4
Related documents......................................................................................................................................... 4
SCOPE AND LIMITATIONS OF TESTING 5
TEST REPORT5
Report Identification....................................................................................................................................... 5
Test Cases Summary Report......................................................................................................................... 5
Defects Summary Report............................................................................................................................... 5
Detected Defects Summary Report.............................................................................................................. 5
Open Defects Summary Report.................................................................................................................... 6
OPEN ISSUES 6
APPENDIX 6

3
PURPOSE OF THE DOCUMENT
This document is to provide a deliverable that will report results of individual test cycles.
Adapt the purpose regarding on the project.

INTENDED AUDIENCE
List the categories of people the document is addressed to; no name lists should appear here.

PROJECT OVERVIEW

Description
Overall project description; a brief description may be enough here since a sub-section refers below to all the
existing documents

Organization and contact responsibilities

Organization 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 question

Name Role Company

e.g. John Doe e.g. Project Manager e.g. SAP

Related documents
Relevant 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).

Category Name Description Location

Presentation containing possible

Data Quality
Data Quality Metrics dashboards for tracking data
Plan
migration quality

Template to capture the organization

structure (people) and process
Data Quality Strategy and
required to capture and report data
Design
quality throughout the data migration
effort.

Testing Outlines an overall test strategy for

Testing Strategy
Strategy the data migration.

Captures test plans by business

Unit Test
object.

Final Data Final Data Quality Documents and reports

Quality Assessment assessment.

4
Assessment

Data Migration Data Migration Test Captures results of individual test

Current Document
Test Results Results cycles.

SCOPE AND LIMITATIONS OF TESTING

Objectives of testing effort, testing priorities and focus. Relevant non scope areas must be reminded here.

TEST REPORT
The 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).

Report Identification
This sub section is aimed to present what has been tested and how. This is kind of a header for the report.
Total number
ID Completed by Date Testing name
of test cases

report project tester name who completed the date of the type of test (e.g. total number
identifier report report unit, integration, of project test
acceptance) cases

Test Cases Summary Report

This sub section contains the status of the different trial runs regarding the test cases that were planned.
Total number of
Trial run % Started % Passed % Failed
test cases

describe the test number of test total number of total number of total number of
period (Week, Month) cases planned to test cases started test cases test cases
there is usually three be run during the / total number of passed / total failed / total
trial runs period test cases number of test number of test
cases cases

Defects Summary Report

Overall status of the defects.

5
Detected Defects Summary Report
This 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.
Total % %
Trail Total % High % Low % High % Low
Closed Medium Medium
Run Defects Severity Severity Priority Priority
Defects Severity Priority
as number number percenta percenta percenta percenta percentag percentag
above of non- of ge of the ge of the ge of the ge of the e of the e of the
rejected closed most mid least most mid least
defects defects critical critical critical urgent urgent urgent
detected defects, defects, defects, defects, defects, defects,
within the regarding regarding regarding regarding regarding regarding
whole the total the total the total the total the total the total
testing defect defect defect defect defect defect
project number number number number number number

Open Defects Summary Report

This 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.
Total
Trail Open % High % Medium % Low % High % Medium % Low
Run Defect Severity Severity Severity Priority Priority Priority
s
as number percentage percentage percentage percentage percentage percentage
abov of of the most of the mid of the least of the most of the mid of the least
e defects critical critical critical urgent urgent urgent
still defects that defects that defects that defects that defects that defects that
open are still are still are still are still are still are still
open open open open open open

OPEN ISSUES

ID Description Owner Open date Due date

6
APPENDIX
Glossary, acronyms, etc.

7
www.sap.com/contactsap

© 2017 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation
to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are
cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the trademarks of their respective companies. See http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark
information and notices.