SAP AG
Version: X.Y Author:
Test Plan Documentation
Project: 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.
© 2010 SAP AG
Project: Version: X.Y Date:
Page 1 of 19
Project:
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: Version: X.Y Date:
© 2010 SAP AG
Test Plan Documentation
Project:
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
Business Process Owner(s) John Smith Klaus Mustermann
Company
Phone
e-Mail
XYZ GmbH XYZ GmbH
+49(1)777-888
[email protected] +49(1)888-777
[email protected]
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
© 2010 SAP AG
Project: Version: X.Y Date:
Page 3 of 19
Project:
Test Plan 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
PRD R/3 system, Automotive
Release 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
DEV Development system
SID of SID of ‘upstream’ - ‘downstream system ’ - system -
QAS
QAS Quality Assurance system
DEV
PRD
PRD Productive system
QAS
-
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 3 4 5 6
‘Upstream’-system means a system where the transports come from ‘Downstream’-system means a system where the transports go to DEV – development system in a transport landscape QAS – quality assurance system in a transport landscape PRD – productive system in a transport landscape
Page 4 of 19
Project: Version: X.Y Date:
© 2010 SAP AG
Test Plan Documentation
Project:
Systems in Transport Landscape 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 Create and assign transport requests to developers Plan functional test in DEV
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
© 2010 SAP AG
Project: Version: X.Y Date:
Page 5 of 19
Project:
Test Plan Documentation
An exception to the standard transport workflow could be necessary to allow fast reaction to urgent problems in the productive system.
Action: Please answer the question:
Exeptions Questions
Answers
Is an exception to this workflow allowed (e.g. for emergency transports)? Who can request those emergency transports?
Yes
No
End User Key User Business Process Owner System Owner (Administrator) Development DD.MM.YYDD.MM.YY
Who is responsible for approval of emergency transports?
Key User Business Process Owner System Owner (Administrator) Development Manager 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
Page 6 of 19
Project: Version: X.Y Date:
© 2010 SAP AG
Test Plan Documentation
Project:
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 Business Department on their own
Activities
Central Test organization in each branch
Central Test organization corporate wide
Central IT department
Project team
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: 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
© 2010 SAP AG
Project: Version: X.Y Date:
Page 7 of 19
Project:
User Acceptance Test
Activities
Test Plan Documentation
Who performs an activity? Every Business Department on their own
Central Test organization in each branch
Central Test organization corporate wide
Central IT department
Project team
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:
Customer Development Test
Activities
Who performs an activity? Every Business Department on their own
Central Test organization in each branch
Central Test organization corporate wide
Central IT department
Project team
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:
Page 8 of 19
Project: Version: X.Y Date:
© 2010 SAP AG
Test Plan Documentation
Project:
Integration Test
Who performs an activity? Every Business Department on their own
Activities
Central Test organization in each branch
Central Test organization corporate wide
Central IT department
Project team
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:
Regression Test
Who performs an activity? Every Business Department on their own
Activities
Central Test organization in each branch
Central Test organization corporate wide
Central IT department
Project team
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:
© 2010 SAP AG
Project: Version: X.Y Date:
Page 9 of 19
Project:
Technical System Test
Activities
Test Plan Documentation
Who performs an activity? Every Business Department on their own
Central Test organization in each branch
Central Test organization corporate wide
Central IT department
Project team
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:
Page 10 of 19
Project: Version: X.Y Date:
© 2010 SAP AG
Test Plan Documentation
Project:
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 maintenance
hot fix 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:
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
© 2010 SAP AG
Project: Version: X.Y Date:
Page 11 of 19
Project:
Test Plan 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
Specific project team (implementation / upgrade / etc.)
Central Test Organization in each branch
Central Test Organization corporate wide
Central IT department
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 need to be tested twice by 2 different persons?
Are there any customer-specific quality targets or criteria?
Which?
Are there special requirements regarding documentation of test cases (paper or electronic)
Which?
Page 12 of 19
Project: Version: X.Y Date:
© 2010 SAP AG
Test Plan Documentation
Project:
Questions
Yes
No
Remark
Are there some legal requirements affecting the test process?
Which?
Is there a person controlling the completeness of the tests?
Who is this person?
Is there a person controlling the correctness of the tests?
Who is this person?
Is there a person controlling the grade of detail of the tests?
Who is this person?
Do you use templates for test case creation?
Example?
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 (unique identfier)
Name of Project
Name of Business Process
Owner of Test Case
Test Type (e.g. Unit, Integration, Regression)
Test System
Client
Detailed description of preparation activities
Detailed description of test procedure
Check / Expected Test Results
Only for Integration Testing: dependencies on other test cases (predecessor and successor)
© 2010 SAP AG
Project: Version: X.Y Date:
Page 13 of 19
Project:
Test Plan Documentation
Test result documentation
Action: Please answer the questions below.
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 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
Master Data
Transactional Data
Actual Test results
Status information
Remarks
Signature
Date of Test
Page 14 of 19
Project: Version: X.Y Date:
© 2010 SAP AG
Test Plan Documentation
Project:
Test KPIs
Action: Please mark in the table below what kind of measurements via predefined KPIs 15 you have regarding reliability of the tests.
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
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
Refresh via client copy from PRD
Refresh via client copy from a standard client in QAS
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
© 2010 SAP AG
Project: Version: X.Y Date:
Page 15 of 19
Project:
Possible method
Yes
No
Test Plan Documentation
Remarks
Manual creation of master data
Automated creation of master data
Manual creation of transaction data
Automated creation of transaction data
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
Page 16 of 19
Project: Version: X.Y Date:
© 2010 SAP AG
Test Plan Documentation
Project:
Test execution Execution
Action: Please answer the questions below.
Execution: Manual or Automated? Question
Yes No
Remark
Do you use manual testing in your current test approach?
Do you use automated testing in your current test approach?
How?
What part (percentage) of the total testing do you perform manually?
Monitoring
Action: Please answer the questions below.
Monitoring Question
Yes
No
Remark
Does the current test approach allow you to have a clear 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?
© 2010 SAP AG
Project: Version: X.Y Date:
Page 17 of 19
Project:
Test Plan 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?
Do you have a defined process in case of test errors (feedback loop / issue tracking) ?
Yes
How does the workflow look like to correct these errors?
No
Tools
Action: Please answer the questions below.
Tools Question Do you use CATT
Yes 16
/ eCATT
17
for testing?
No
Remark
Are there any 3rd party tools involved in your current test 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
Page 18 of 19
Project: Version: X.Y Date:
© 2010 SAP AG
Test Plan Documentation
Project:
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.
© 2010 SAP AG
Project: Version: X.Y Date:
Page 19 of 19
