SAP S/4HANA Cloud Test Management:

Guide and Best Practices

SAP Activate
June 2021

PUBLIC
Purpose

The purpose of this accelerator is to provide detailed guidance on how to organize, manage, and
conduct testing during key phases of your SAP S/4HANA Cloud implementation. This guide also
organizes existing testing templates, tools, and resources in one central place for convenience.

This accelerator outlines:

 An overview of the common types of testing

 Guiding principles and best practices
 Phase activities and the available accelerators and resources

After reviewing this guide, members of the project team should have a clear understanding of
test management as well as direction on how testing should be conducted. This framework of
expectations, combined with access to useful tools, will help guide team members along the way
and ensure successful outcomes are met.

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Test Management Guide
Table of Contents:

I. Overview
Common Types of Testing
Testing Challenges

II. Guiding Principles/Best Practices

How to Approach Testing- Planning, Execution, & Monitoring
What is a Test Strategy, Plan and Schedule

III. Key Testing Activities and Available Resources/Tools

Detailed View of Testing Activities in Activate Phases
List of Accelerators

IV. Overview of Manual Testing, CALM, and Test Automation Tool

Manual vs. Automated Testing
Intro to SAP Testing Tools
1. Manual Testing
2. SAP Cloud Application Lifecycle Management
3. SAP S/4HANA Cloud Test Automation Tool
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3
Section I. Overview
-Common Types of Testing
-Testing Challenges
Test Management Overview
Test Management and planning can help reduce time, costs, and potential risks associated with
software changes. Testing in S/4HANA Cloud is conducted to ensure the activated and pre-
Visual:
delivered end-to-end business processes work with specific configuration and data.

Common Types of Testing:

Unit Test
 Unit Testing- A unit test is intended to isolate and test a informal
single piece of functionality. This may be a single
application, report, or interface action, typically informal
and performed with a small set of data/scenarios.

 Integration Testing- An integration test that includes

interfaced data from or to other systems in the end to end End to End Test
Integration Test
test, usually performed in the QA system. This formal formal
formal
testing ensures data can be imported, exported or
reported on as needed in the SAP S/4HANA Cloud or in
the interfaced system.

 End to End Testing- End to end testing covers an end to

end flow with multiple units or strings within a single
system. This formal testing may cover entire scope items
or extend beyond a single scope item.
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5
Potential Challenges of Testing

When testing an application, the team may face many challenges and roadblocks. Being able to
identify these in the early stages of testing can help decrease potential issues and delays.
Test Users may encounter these common scenarios:
 Insufficient or undefined standards- There can be a misunderstanding
of business processes among project team members. This can be the
result of missing or inadequate documentation or undefined testing
requirements/guidelines. In some cases, the test strategy or plan is not
developed during the early stages of the project.

 Unstable testing environment- Failed integration or interface issues may

occur. Users may experience roadblocks/software bugs when testing
integrated systems, affecting project timelines and risks.

 Lack of Communication- Communication gaps can lead to inadequate

testing. When team members do not openly discuss configuration changes
or present status updates, it can create hurdles in creating accurate test
cases.
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6
II. Guiding Principles/Best Practices
-How to Approach Testing- Planning, Execution, & Monitoring
-What is a Test Strategy, Plan and Schedule
Test Management Guiding Principles
Following a set of key guiding principles throughout the testing process is a guaranteed way to
ensure testing is organized and running efficiently throughout every project implementation.

Key Principles and Best Practices: 

 Discuss testing during early stages of the project

 Set realistic timing and scheduling expectations

 Clearly defined deliverables should be provided

 Once scheduling is complete and deliverables are defined, a testing

approach can be developed

 Design test plans based on business requirements

 Continuously execute tests to validate the business requirements

 Track testing results to determine effectiveness of strategy 

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

How to Approach Testing: 3 Key Focal Points

Plan & Prepare

Execute  Analyze & Monitor 
(Test Management)
 Define the project testing at a basic  Assigned resources conduct their  Test results are assessed and
level unit, integration, and end to end modified with any business
 Outline the business requirements, testing requirement changes
goals, and purpose of testing  Results are tracked and recorded  Adjust schedules and resources
 Roles and responsibilities are clearly  Communication with project team to meet new requirements
defined to update status and modify  Progression of testing is
 A testing strategy and plan are requirements as needed measured and evaluated
developed, detailing a schedule with  Testing is completed and  Changes are monitored and
key activities, milestones and deliverables are met issues are addressed
available resources

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

What is a Test Strategy?
A test strategy is a roadmap which defines
how testing will be conducted for the duration of
the project. It typically is a document that
contains the project testing objectives,
processes and deliverables, as well as roles
and responsibilities. Simply stated, the strategy
outlines the “why, “what”, “who” and “how.”
Project team members and stakeholders should
align and approve the testing approach before
completing testing activities.

The test strategy document is helpful in

guaranteeing teams are aligned as they
execute testing.
Example of a test strategy overview (left).

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

What is a Test Plan?
A test plan is a general overview of what the
project team hopes to achieve. It typically
includes an outline of test descriptions, success
criteria, testing methods and status. Test plans
can detail what the expected outcomes are,
what capabilities will be reviewed and how
testing will be conducted. They are dynamic and
can be revised as business requirements
change.

Risk-based test planning helps analyze the

impact of software changes on critical business
processes. This catalog of activities can serve
as a blueprint for running the tests needed to
ensure the software is working properly.
Example of a test plan (left).

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11

What is a Test Schedule?

A test schedule includes the necessary testing

resources and target start and end dates of each
task. It is a daily and weekly overview of assigned
responsibilities and is included in the overall test
plan.

The test schedule is vital in ensuring deadlines are

met and any potential issues and risks are tracked
and monitored. It is important to monitor the
schedule often to be aware of resource availability
and activities. This will allow the project team to
anticipate any potential delays or changes to
expected outcomes.
Example of test schedule (left).

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12

III. Key Testing Activities and Available
Resources/Tools
-Detailed View of Testing Activities in Activate Phases
-List of Accelerators
 Key Testing Activities in Activate Phases:
Unit Test String Test Business Process Test Integration Test User Acceptance Test Data Migration Test Business Acceptance
Test
• Test a single piece • More than one • A business process • Extends beyond a • Key Users and • Business Process • Key Users and End
of functionality related unit tests test covers an end business process Business Users Expert and Key
Users confirm that
• Single application, are done one after to end flow with tests and ensures execute the business Users test the load
processes can be
report, or interface the other to form a multiple units or that data can be process tests or of production-like
executed as agreed,
action string strings within a imported, exported system integration data into the Q-
meeting their daily
• Multiple variants • Check the flow of single system or reported on as test as relevant system, along with
job requirements
depending on the data from one • Cover entire scope needed in the SAP • Confirm that the any follow up • Indication of user
anticipated application to items or extend S/4HANA Cloud or process can be actions necessary
system
business process, another beyond a single in the interfaced executed as agreed
understanding and
and configuration scope item system in the fit-to-standard
business readiness
done workshop

Explore  Realize Deploy

Sprint 1 Sprint 2 Sprint 3-n
 Create Test Strategy
Configuration Configuration Configuration Data Migrate
 Define Test Team

Unit/String Test Unit/String Test Unit/String Test Data Migration Test

Business Process Business Process

Tests Tests Business Acceptance
Test
System Integration
Test

User Acceptance Test User Acceptance Test

Prepare Test Plan Prepare Test Plan Prepare Test Plan Prepare Test Plan
Sprint 1 Sprint 2 Sprint 3 Sprint 4
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 14
Activate Phases Resource List-
Links to Key Tools/Accelerators to Assist Testing Activities:

Prepare  Explore Realize Run

 Availability and Dep  Detailed Test Sche  Test Phase Kick Off  Automated Test Sc
endencies of Scope dule Template.xlsx Template.pptx (Publi ripts Change Histo
Items.xlsx (SAP Cus (SAP Customer) c) ry.xlsx (SAP Custo
tomer) mer)

 SAP S/4HANA Clou  Test Automation To  User Manual BPD P  Test Script Releas
d Onboarding Prese ol for SAP S4HAN rocess Dependencie e Change Informati
ntation.pptx (SAP C A Cloud.pptx (Publi s.docx (Public) on.xlsx (Public)
ustomer) c)

 What's New in SAP  Test Strategy Tem

S/4HANA Cloud.pdf plate S4HANA Clo  What's New in Testi  Help - SAP S/4HA
(Public) ud.pptx (SAP Cust ng.pptx (Public) NA Cloud (Public)
omer)

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 15

IV. Overview of Manual Testing, CALM, and Test
Automation Tool
-Manual vs. Automated Testing
-Intro to SAP Testing Tools
1. Manual Testing
2. SAP Cloud Application Lifecycle Management
3. SAP S/4HANA Cloud Test Automation Tool
Manual Testing Versus Automated Testing: Quick Comparison

Manual Testing Automated Testing

Flexibility Inconsistent Advanced Faster

Customized
VS Immediate Time to Set-up
Time Consuming

Quick Adjustments
Needed Often
Adaptability

Can Re-use Less Errors

Tedious

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 17

Manual Versus Automated Testing- Detailed View
Manual Testing
Benefits: Greater flexibility and adaptability- users
can easily change test cases and be creative with
scenarios. Testers may be able to quickly combat
errors and issues as they arise.
Weaknesses: Manual tests can be inconsistent as
test users may make errors or may not fully
understand the business processes. Manual work
can also be tedious and time consuming if a plan
is not in place beforehand.
Opportunities: Overall, manual testing is quick to
launch. It can handle great complexity and be
customized to fit advanced user processes.
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
Automated Testing
Benefits: Allows users to run tests simultaneously
and in parallel with one another. Existing cases can
be copied and re-used in other scenarios. Test
results are immediate.
Weaknesses: Existing test cases need to be
adjusted when business requirements change. Not
all tests can be automated due to complexities.
Automation takes time to set up and may require
advanced knowledge.
Opportunities: While automated testing may be
slower to launch, it’s generally faster than manual
operations and less prone to human error.
18
 Testing Tool I
Manual Testing w/ Key Documents
If testers prefer manual way of organize, manage, and conduct testing, SAP provides various templates to help and guide
the testers how to plan, prepare, execute testing and be able to analyze & monitor the entire testing process.

Plan Prepare Execution

 Test Kickoff Presentation  Test Strategy  Detailed Test Schedule  Manual Test Script Template
• This document is to • This is an accelerator to • This document is to plan • This is a generic template
initiate and establish align on the test strategy tests across multiple for tracking and
communication within test to ensure that business phases and weekly *monitoring (refer below dashboard)
project team and set process execute as sprints and track test test cases based on the
goals and plan timelines anticipated along with preparation and scripts for scope items
to manage successful test users execution and can be modified
(*other topics not covered by the Best Practice
testing scrips but should be tested like integration tests
and customer specific)

Analyze & Monitor Test Case Monitoring Dashboard from manual test script template
TEST PLAN DASHBOARD
Scope Test Script/Business Scenario Tab Status Steps Pass Fail On hold N.A. Owner Due Date Comment
Finance J58 - Accounting and Financial Close J58 in process 72 0 1 0 1 Name 1 1/31/2018
Finance J59 - Accounts Receivable J59 in process 47 0 1 0 1 Name 2 1/31/2018
Finance J60 - Accounts Payable J60 not started 57 0 1 0 1 Name 3 1/31/2018
Finance J62 - Asset Accounting J62 in process 45 0 1 0 1 1/31/2018
Finance J77 - Bank Account Management - Extra J77 not started 17 0 1 0 1 1/31/2018
Finance J78 - Cash Operations - Extra J78 not started 10 0 1 0 1 1/31/2018
Finance 1GP - Intercompany Processes - Cost Allocation in General Ledger 1GP completed 8 0 1 0 1 1/31/2018
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 19
Testing Tool II
SAP CALM Tool Overview Cloud Application Lifecycle Management
Cloud-based implementation and operation platform serves as a liaison between LOB and IT providing content-driven
implementation project guides with processes, tools, services and an organizational model to manage the complete
application lifecycle. Additionally, integrates with automated testing tool to prepare and execute tests. (Tip!:
What’s new in SAP Cloud ALM)
5 Core Capabilities

SAP Cloud ALM 1.

Self-guided and content-driven implementation based on SAP Activate
methodology and Best Practices content

Fast onboarding of project Teams and Progress Monitoring of

2 implementation activities

Test Management Test Execution Tracking Manage Implementation Tasks: automatically generated and adapted
3. to customer scope

 Manual  Test Scope

 Test Scope Execution
Functional Supports Fit-to-Standard workshops with convenient visualization of
Management
Testing Monitoring 4. Business Models and Process Descriptions
 Test Scope  Project Task
 Automated
Execution Monitoring
Functional
Monitoring Prepare and manage manual and automated tests with integrated
Testing Auditing

5. reporting capabilities

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 20

Testing Tool II
SAP CALM Tool – Key Functionalities
Plan Prepare Execution Analyze & Monitor
 Test Readiness Overview  Test Case Overview  Test Execution Overview  Test Overview
 Prepare tests on  Define the structure  Create ‘Test Actions’  Testing Overview
process based on and scope of manual for selected business o Preparation by status
processed scoped and test cases activities o Test Execution by Status
requirements  Create & prepare the  Review & ‘Run Test’ o Test Run History
 Identify content for manual or execute test cases  Project Overview
implementation test cases with ‘Test Case o Next Milestone
progress by process  Manage automated Prepared’ status’ o Completeness of tasks
flow and status test case from the test  Close a test run when
 Define test readiness automation tool for overall status is green
SAP S/4HANA Cloud

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC * New integration feature released as of Q2/2021 21
Testing Tool III
SAP S/4HANA Cloud Test Automation Tool Overview
Test Automation tool is integral part of S/4HANA Cloud and can be used to automate business process testing
leveraging form pre-delivered test scripts and to change exiting or to create new test cases via a recording functionality
during implementation. (Tip!: Helpful Test Automation Tool Document)

5 Main Business Benefits

Accelerate business process and regression
SAP S/4HANA Cloud 1. Acceleration tests

Reach a high test coverage even during short

2. Accurate test cycles like upgrade tests

Manage Your Test Analyze Test Create or adapt test scripts via recording
Process
Test Your Process
Result 3. Configurable functionality
 Dashboard
 View Standard  Create/Edit  Process
Test Process Test Plan Document all automated tests activities with
 Create/Edit
Execution 4. Documentation
 Create, Copy, screenshots
Status
Edit Test Data Variant  Test Execution
Process  Schedule and
Status
 Change Execute Test  Test Results,
Visibility on Plan
Analytics, &
5. Analysis Results dashboard with drill down functionality
Test Plan  View Logs/Print
Graphs
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 22
 Testing Tool III
SAP S/4HC Test Automation Tool - Key Functionalities
Plan Prepare Execution Analyze & Monitor
 Create & Configure Test  Manage Your Test  Manage Test Plan & Test  Analyze Automated Test
User Process Your Process Results
 Create test user  Create & Copy Test  Create Test Plan  Automated test result
 Configure to allow Process  Define Data Variants in a dashboard
users to execute  Add, Edit Actions  Define Binding  Review by category
testing accordingly  Review Action ID Parameters o Customer test plans
o Total test processes
 Enable Change  Schedule & Execute Executed
Visibility

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 23

Thank you.
Contact information:
SAP Activate
SAPActivateMethodology@sap.com