Template Test Plan V10

SAP AG
Version: X.Y
Author: <name>
Test Plan Documentation
Project: <name>
History
Version Date Comments (Author)
X.Y
About this Template

You use this template to document how the testing of this project will be organized. The document is
organized as a type of questionnaire.
This document contains form elements to simplify the data entry but it requires to be in protected mode
in order to enable the form entry.
© 2021 SAP AG Project: <name> Page 1 of 19

Version: X.Y
Date:
Project: <name> Test Plan
Documentation
Table of Contents
Roles and Responsibilities for Testing......................................................................................3
Transport Landscape.................................................................................................................................. 4
Roles, Responsibilities and Workflow....................................................................................................... 5
Change request............................................................................................................................................ 6
Current Test Strategy..................................................................................................................7
Activities distribution.................................................................................................................................. 7
Definition of test scope............................................................................................................................. 11
Development of tests................................................................................................................................. 12
Customer specific quality targets and criteria........................................................................................ 12
Test Case description................................................................................................................................ 13
Test result documentation........................................................................................................................ 14
Test KPIs.................................................................................................................................................... 15
Test data preparation and management.................................................................................................. 15
Test execution........................................................................................................................... 17
Execution.................................................................................................................................................... 17
Monitoring.................................................................................................................................................. 17
Error Tracking............................................................................................................................................ 18
Tools ..................................................................................................................................................... 18
Page 2 of 19 Project: <name> © 2021 SAP AG

Version: X.Y
Date:
Test Plan Project: <name>
Documentation
Roles and Responsibilities for Testing

 Action: Please enter information about Test Management roles and responsibilities and provide the
contact details of the persons in these roles.
Example:
Role / Area Responsible Company Phone e-Mail
Business Process Owner(s) John Smith XYZ GmbH +49(1)777-888 john.smith@xyz.com
Klaus XYZ GmbH +49(1)888-777
klaus.mustermann@xyz.com
Mustermann
Roles
Role / Area Responsible Company Phone e-Mail
Executive Sponsor

Test Project Manager(s) /

Test Coordinator(s)
Application

implementation / operation
Technical implementation /

operation
Business Process Owner(s)

Key / Power User(s)

Test Case Development


Version: X.Y
Date:
Documentation
Transport Landscape
Please describe the transport landscape of the chosen solution in the tables below.
 Action: In this table please enter the information regarding productive systems in the landscape.
Example:
SID1 System role Release
PRD R/3 system, Automotive 4.7 SR 2
Productive system
SID System role Release

 Action: In this table please enter the information about each system in the transport landscape. This
includes the SID of the ‘upstream’ 2- and ‘downstream’ 3-systems for each system in the landscape.
As soon as the table is completed, it describes the whole transport landscape and the transport routes in the
landscape.
Example: the table below describes the classical 3-systems landscape DEV 4 -> QAS 5 -> PRD 6. Here PRD is
a downstream-system for QAS and DEV is upstream-system for QAS:
SID Role in the transport landscape SID of SID of
‘upstream’ - ‘downstream
system ’ - system
DEV Development system - QAS

QAS Quality Assurance system DEV PRD
PRD Productive system QAS -
Systems in Transport Landscape
1
SID – System ID. The name for your SAP system which is unique throughout your organization and must consist of exactly three alphanumeric characters
where only uppercase letters are allowed and the first character is a letter (not a digit)
2
‘Upstream’-system means a system where the transports come from
3
‘Downstream’-system means a system where the transports go to
4
DEV – development system in a transport landscape
5
QAS – quality assurance system in a transport landscape
6
PRD – productive system in a transport landscape

Version: X.Y
Date:
Documentation
SID Role in the transport landscape SID of SID of

‘upstream’ - ‘downstream
system ’ - system

Roles, Responsibilities and Workflow
 Action: Please describe in the column ‘Project, Name and Role’ who is responsible for each particular
step in the change management and the corresponding role. If they are different for several projects please
enter the information for each project in one field using a project short name as a prefix.
Example:
Step / Function Project, Name and Role
Perform functional test in DEV PSAP_R3 - J.Smith, Test Manager;
SCM_SAP - S.John, Test Manager
Roles in Change Management

Step / Function Project, Name and Role
Decision about software projects <Please type in your answer here>
Create and assign transport requests
<Please type in your answer here>
to developers
Plan functional test in DEV
<Please enter your answer here>
Perform functional test in DEV
Transport into QAS
Monitor result of import in QAS
Plan test in QAS
Perform test in QAS
Approval of test
Import into PRD
Monitor result of import in PRD
An exception to the standard transport workflow could be necessary to allow fast reaction to urgent problems
in the productive system.

Version: X.Y
Date:
Documentation
 Action: Please answer the question:

Exeptions
Questions Answers
Is an exception to this workflow Yes No
allowed (e.g. for emergency
transports)?
Who can request those emergency End User

transports?
Key User
Business Process Owner
System Owner (Administrator)
Development
<Other>DD.MM.YYDD.MM.YY
Who is responsible for approval of Key User

emergency transports?
Business Process Owner
System Owner (Administrator)
Development Manager
<Other>DD.MM.YYDD.MM.YY
DD.MM.YYDD.MM.YY
Change request
 Action: Please mark the appropriate field if there is any standard change request form in use in the
company and if there is a change request database storing the requests, which are already processed.
Change Request Form and Database

Questions Answers
Change request form available? Yes
No
Change request database available? Yes
No

Version: X.Y
Date:
Documentation
Current Test Strategy
Activities distribution
 Action: Please use the tables below to describe how the test activities are assigned to organizational
units in the company. We are interested in the following test types: Unit Test 7, User Acceptance Test 8,
Customer Development Test 9, Integration Test 10, Regression Test 11 and Technical System Test 12. For each
activity in each table, please mark the appropriate organizational units (one or more) which are responsible for
this particular activity.
If there are any comments or additions regarding activities distribution please use the field under the table.
In each table for each activity mark at least one responsible organizational unit.
Unit Test Who performs an activity?
Every Central Test Central Test Central IT Project team <Other>

Business organization organization department
Department in each corporate
Activities on their own branch wide
to decide what needs to be

tested
to create test case descriptions
to organize testing
to execute test
to monitor test
to evaluate test results
Comment to the table above: <Please enter your comment here>
7
Unit Test – the lowest level of testing where the program or transaction is tested and evaluated for errors
8
User Acceptance Test – represents end-to-end testing from the business perspective. The purpose of that is to prove that initial business requirements were
implemented exactly and in accordance to specifications made before
9
Customer Development Test – mixture of Unit Test and Integration Test with scope limited to the customer’s own development
10
Integration Test – is accomplished through the execution of predefined business flows, or scenarios, that emulate how the system will run your business.
Integration Test starts with the testing of the cross-functional integration points and ends with the end-to-end testing of critical business processes
11
Regression Test – test of critical business processes after a change to ensure that a) any problem has been fixed and that no other previously working
functionality has been harmed as a result of the changes and/or b) that newly added features working as designed and have not created any unexpected side
effects
12
Technical System Test – test aimed to verify the production system environment from a technical standpoint, e.g. to test if the system can be started /
stopped properly, if the basis technical infrastructure is working fine and the whole system in conjunction with database and operating system performs well
from technical point of view. Among this the following technical tests are usually part of Technical System Test: backup and recovery, system administration,
printing and faxing, failure scenarios, disaster recovery

Version: X.Y
Date:
Documentation
User Acceptance Test Who performs an activity?


tested
to organize testing
to execute test
to monitor test
Customer Development
Who performs an activity?
Test

tested
to organize testing
to execute test
to monitor test

Version: X.Y
Date:
Documentation
Integration Test Who performs an activity?


tested
to organize testing
to execute test
to monitor test
Regression Test Who performs an activity?


tested
to organize testing
to execute test
to monitor test

Version: X.Y
Date:
Documentation
Technical System Test Who performs an activity?


tested
to organize testing
to execute test
to monitor test

Version: X.Y
Date:
Documentation
Definition of test scope
 Action: Please use the table below to document how you evaluate which test cases are needed for specific software
changes and software maintenance. In other words, which methods and strategies are in use to help in decision of which
test cases should be executed after a change of a specific type?
Test Scope
Change type
Possible methods projects regular hot fix
maintenance process
General regression testing of all core business processes
Analysis of changed / new objects and affected application area
Evaluation of customizing settings to identfy which processes are configured

and therefore most likely used and potentially affected by changes
Evaluation of load profile (e.g. EWA 13, ST14, RBE 14, etc.) to find the business
processes with a high load (meaning that such processes could also be most
critical for everyday work)
Only new functionality will be tested, usually no Regression Testing
Others: <Please enter an additional method here if there is any>
13
EWA – Early Watch Alert
14
RBE - Reverse Business Engineer - a tool used for process-oriented analysis and continual optimization of SAP production systems. Using data from
production systems it is possible to analyze how functions in the SAP System are used and identify potential for improvement

Version: X.Y
Date:
Documentation
Development of tests
 Action: Please use the table below to specify who is responsible for developing test cases. Please also
specify what kind of testing is meant (manual or automated).
Development responsibility
Options Manual Automated Remarks
Every Business Department on its own <Please enter your comment here>
Specific project team (implementation / <Please enter your comment here>

upgrade / etc.)
Central Test Organization in each branch <Please enter your comment here>
Central Test Organization corporate wide <Please enter your comment here>
Central IT department <Please enter your comment here>
<Please put in an additional option here if <Please enter your comment here>
there is any>
there is any>
Customer specific quality targets and criteria
Completeness of any test plays an important role in the total success of the test. A complete test of a complex
business scenario very often cannot be created without participation of the people who deal with the scenario
in their day-to-day work.
As the major goal of any test activity is to get reliable results, a controlling of correctness, completeness and
grade of detail is very important.
 Action: Please answer the questions below.
Quality targets and criteria

Questions Yes No Remark
Is the ‘2-person policy’ in use, i.e. test cases <Please enter your comment here>
need to be tested twice by 2 different persons?
Are there any customer-specific quality targets Which?
or criteria? <Please enter your comment here>
Are there special requirements regarding Which?
documentation of test cases (paper or <Please enter your comment here>
electronic)
Are there some legal requirements affecting the Which?
test process? <Please enter your comment here>

Version: X.Y
Date:
Documentation
Questions Yes No Remark

Is there a person controlling the completeness Who is this person?
of the tests? <Please enter your comment here>
Is there a person controlling the correctness of Who is this person?
the tests? <Please enter your comment here>
Is there a person controlling the grade of detail Who is this person?
of the tests? <Please enter your comment here>
Do you use templates for test case creation? Example?
<Please enter your comment here>
Test Case description
 Action: Please use the table below to specify what information is included in the standard test case
description adopted to use in the company.
Information in Test Case description
Information Available Remarks

Test Case ID <Please enter your comment here>
(unique identfier)
Name of Project <Please enter your comment here>
Name of Business Process <Please enter your comment here>
Owner of Test Case <Please enter your comment here>
Test Type (e.g. Unit, Integration, Regression) <Please enter your comment here>
Test System <Please enter your comment here>
Client <Please enter your comment here>
Detailed description of preparation activities <Please enter your comment here>
Detailed description of test procedure <Please enter your comment here>
Check / Expected Test Results <Please enter your comment here>
Only for Integration Testing: dependencies on <Please enter your comment here>
other test cases (predecessor and successor)
<Please enter an additional option here if <Please enter your comment here>
there is any>
Test result documentation

Version: X.Y
Date:
Documentation
Handling of Test Results
Question Yes No Remark

Do you document the results of the manual testing? How?
Do the currently used tools allow the tester to document <Please enter your comment here>
the test results (results such as what has been tested by
whom, when and with which results)
 Action: Please use the table below to specify what information is included in the standard test result
documentation adopted to use in the company.
Information in Test Result Documentation

Information Available Remarks
Name of Tester <Please enter your comment here>
Master Data <Please enter your comment here>
Transactional Data <Please enter your comment here>
Actual Test results <Please enter your comment here>
Status information <Please enter your comment here>
Remarks <Please enter your comment here>
Signature <Please enter your comment here>
Date of Test <Please enter your comment here>
there is any>
Test KPIs
 Action: Please mark in the table below what kind of measurements via predefined KPIs 15
you have
regarding reliability of the tests.
15
KPI - key performance indicator - a measurement or metric for evaluating a company's business strategy, performance, or technology. KPI express abstract
company objectives in financial or physical units for comparative purposes

Version: X.Y
Date:
Documentation
Test KPIs
Possible measurement Yes No Remark

General Stability
Availability / unplanned downtime

Performance
No. of short dumps

No. of update-errors
No. of trouble tickets (per component)

Interface throughput
<Please enter additional measurements if there are any>

Test data preparation and management
 Action: Please describe what methods you use to prepare the data in QA system database before
testing.
Test Data Preparation

Possible method Yes No Remarks
Refresh via system copy of PRD <Please enter your comment here>
Refresh via client copy from PRD

Refresh via client copy from a standard client in QAS

Manual creation of master data

Automated creation of master data

Manual creation of transaction data

Automated creation of transaction data

<Please enter an additional method if there is any>


Version: X.Y
Date:
Documentation
 Action: Please describe what methods you use to manage the test data (to create it, to store it, to update
it, etc.) for testing.
Test Data Management
Possible method Yes No Remarks

Microsoft Office Excel spreadsheets
Local or central test data databases

What kind of databases?
Paper
Automated Test Tools

Test data is not managed centrally and is up to a tester

<Please enter an additional method if there is any>


Version: X.Y
Date:
Documentation
Test execution
Execution
Execution: Manual or Automated?

Do you use manual testing in your current test approach? <Please enter your comment here>
Do you use automated testing in your current test approach? How?

What part (percentage) of the total testing do you perform <Please enter your comment here>
manually?
Monitoring
Monitoring
Does the current test approach allow you to have a clear <Please enter your comment here>
picture of the testing progress at every point of time?
Does the current test approach allow you to estimate
whether the time schedule is going to be kept?
Does the current test approach allow you to have an
overview of the actual test results?
Does the current test approach allow you to react as
required in case of error?

Version: X.Y
Date:
Documentation
Error Tracking
 Action: Please describe the workflow for error tracking established in the company.
Error Tracking
Questions Answers
Who is involved in case of an error during tests in QAS? <Please enter your answer here>
Do you have a defined process in case of test errors Yes No

(feedback loop / issue tracking) ?
How does the workflow look like to correct these errors? <Please enter your answer here>
Tools

Tools

16 17
Do you use CATT / eCATT for testing? <Please enter your comment here>
Are there any 3rd party tools involved in your current test <Please enter your comment here>
approach?
Are there any tools used for assignment of testers?
Are there any tools used for execution of tests and

documentation of results?
Are there any tools used to follow-up in case of error?
Are there any tools used to manage test data?

16
CATT - Computer Aided Test Tool - an SAP tool enabling you to combine and automate business processes as repeatable test procedures
17
eCATT - extended CATT - a successor of SAP CATT which provides more flexibility and functionality. Delivered starting with the basis release 6.20 of the
SAP Web AS

Version: X.Y
Date:
Documentation
Copyright 2009 SAP AG. 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 AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other
software vendors.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge and other SAP products
and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in
Germany and in several other countries all over the world. All other product and service names mentioned and associated
logos displayed are the trademarks of their respective companies. Data contained in this document serves informational
purposes only.
National product specifications may vary.
The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your
license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and
functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business,
product strategy, and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does
not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this
material. This document is provided without a warranty of any kind, either express or implied, including but not limited to
the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential
damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross
negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that
you may access through the use of hot links contained in these materials and does not endorse your use of third-party
Web pages nor provide any warranty whatsoever
relating to third-party Web pages.

Version: X.Y
Date:

Template Test Plan V10

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Template Test Plan V10

Загружено:

Авторское право:

Доступные форматы

SAP AG

Test Plan Documentation

About this Template

© 2021 SAP AG Project: <name> Page 1 of 19

Page 2 of 19 Project: <name> © 2021 SAP AG

Roles and Responsibilities for Testing

© 2021 SAP AG Project: <name> Page 3 of 19

PRD R/3 system, Automotive 4.7 SR 2

DEV Development system - QAS

Page 4 of 19 Project: <name> © 2021 SAP AG

SID Role in the transport landscape SID of SID of

Roles, Responsibilities and Workflow

Roles in Change Management

© 2021 SAP AG Project: <name> Page 5 of 19

 Action: Please answer the question:

Who can request those emergency End User

Who is responsible for approval of Key User

Change Request Form and Database

Page 6 of 19 Project: <name> © 2021 SAP AG

Current Test Strategy

Unit Test Who performs an activity?

Every Central Test Central Test Central IT Project team <Other>

to decide what needs to be

© 2021 SAP AG Project: <name> Page 7 of 19

User Acceptance Test Who performs an activity?

Every Central Test Central Test Central IT Project team <Other>

to decide what needs to be

to decide what needs to be

Page 8 of 19 Project: <name> © 2021 SAP AG

Integration Test Who performs an activity?

Every Central Test Central Test Central IT Project team <Other>

to decide what needs to be

Regression Test Who performs an activity?

Every Central Test Central Test Central IT Project team <Other>

to decide what needs to be

© 2021 SAP AG Project: <name> Page 9 of 19

Technical System Test Who performs an activity?

Every Central Test Central Test Central IT Project team <Other>

to decide what needs to be

Page 10 of 19 Project: <name> © 2021 SAP AG

Definition of test scope

Analysis of changed / new objects and affected application area

Evaluation of customizing settings to identfy which processes are configured

Others: <Please enter an additional method here if there is any>

© 2021 SAP AG Project: <name> Page 11 of 19

Specific project team (implementation / <Please enter your comment here>

Central IT department <Please enter your comment here>

Customer specific quality targets and criteria

 Action: Please answer the questions below.

Quality targets and criteria

Page 12 of 19 Project: <name> © 2021 SAP AG

Questions Yes No Remark

Test Case description

Information Available Remarks

Name of Business Process <Please enter your comment here>

Owner of Test Case <Please enter your comment here>

Test System <Please enter your comment here>

Client <Please enter your comment here>

Detailed description of preparation activities <Please enter your comment here>

Detailed description of test procedure <Please enter your comment here>

Check / Expected Test Results <Please enter your comment here>

Test result documentation

 Action: Please answer the questions below.