Solution Manager

Component Based Test

Automation - CBTA

Presenters - Guy Pengelly and Harald Ahorner

May 2015
Contents

Overview

The Journey

Where CBTA fits in Solution Manager

Should we automate tests?

Show Me

Lessons Learned

NZSUG – May 2015

 Overview
Challenges at NZDF

• It’s a big (eco-)system

• We will be doing more testing -

‒ with less people
‒ who don’t have the institutional knowledge

• We will be introducing more change

‒ with the same restrictions

• The system is/will be necessarily harder to manage

‒ with the same restrictions

• Unhappy customers

3
NZSUG – May 2015
 The Journey
Run SAP like a factory with Solution Manager ?

Facilitate and simplify administration → Job scheduling and documentation

Facilitate and simplify monitoring → Process, technical, PI monitoring

Back-office analysis → End User Experience Monitoring

Back-office analysis → Custom Code Lifecycle Mgmnt

Documentation → Reverse Business Process Engineering

More structured change process → Change Request Mgmnt

Target and automate testing → Change analysis, Test Mgmnt, CBTA

4
NZSUG – May 2015
 Overview
What is Component Based Test Automation (CBTA)?
• CBTA provides a platform for creating and executing test scripts

• CBTA is integrated with other SAP Solution Manager components

‒ Business hierarchy

‒ Change analysis

‒ Test management

‒ Change management ..and what it’s not

• It’s free to use
• There are technical limitations

• Automated testing is NOT the silver bullet

• Automated testing demands some serious up-front

investment in time

5
NZSUG – May 2015
 Overview
What can we do with CBTA
We can use CBTA to test: We can execute tests:
‒ SAP Gui ‒ Individually
‒ SAP Business Server Pages (BSP) ‒ Collectively
‒ SAP CRM web client ‒ Live
‒ SAP ABAP Webdynpro (native only) ‒ Scheduled
‒ SAP java webdynpro ‒ Repetitively with imported data sets
‒ SAP web GUI (for html)
‒ SAP Portal

The following applications are currently not support by CBTA

‒ Adobe Flash
‒ Java Applets
‒ SilverLight
‒ Other UI Technologies e.g. Web AJAX Framework

6
NZSUG – May 2015
 How?
The Process
• Set up
‒ Build the process hierarchy with executables
‒ Set-up & schedule Tbom creation
‒ Create test scripts for the executables

• Execution
‒ Run a change analysis for a change
‒ Optimize the test scope to a manageable test set
‒ Build test plan/packages
‒ Assign to testers
‒ Execute tests
‒ Record results in test plan

7
NZSUG – May 2015
 Context
The business process hierarchy
How do you do it?
The business process hierarchy links:
‒ Test script
‒ Documentation
‒ Transaction/Programme
‒ TBom

What do you do?

With which technical components?

8
NZSUG – May 2015
 Context
Test scripts and Solution Manager

9
NZSUG – May 2015
 Context
Change analysis with UPL
Solution Manager Managed System(s)

Various Technical Objects

Business Process/Step Test scripts

Executable Unit

Technical Bill of Materials

(TBOM)

Technical Objects

‒ Which business process is this method used in?

‒ What should I test?

10
NZSUG – May 2015
 Context
Optimising a test plan

11
NZSUG – May 2015
 Context
Test execution

12
NZSUG – May 2015
 Should we?
The decision to automate a test script or not?
Deloitte have created a framework that analyses whether a test script is a good
candidate for automation using criteria such as:

‒ Reusability

‒ Number of iterations of the test script

‒ Complexity to automate

‒ Other….

Based on this an informed decision

is made on whether the test script
is suitable for automation.

13
NZSUG – May 2015
 Show Me…
Demonstration
Create a simple test script and assign to the business process hierarchy

Execute and get the result

• Create Asset

14
NZSUG – May 2015
 Show Me…
Demonstration
Run a complex test script using a test data container

• Release Employee

15
NZSUG – May 2015
 Lessons Learned
What we’ve found on the journey
• Building test scripts is like any other software development process. Tools like screen
recording help, but you need to:
‒ Understand the recording (component library)
‒ Have a framework to design and organise in place (e.g. naming conventions, library
of reusable patterns, design patterns etc)

• An initial investment to understand and learn the tool is required, it is not self-
explaining.

• Master Data must be accurate, before you can start running a script. This part must not
be under estimated.

• The test assessment should be done first to determine the effort against the value
delivered.

17
NZSUG – May 2015
 Lessons Learned
What we’ve found on the journey
• Simple GUI processes are easier to script within CBTA.

• Complex end-to-end business processes using ABAP WebDynpro are difficult to

implement and require manual development work during the test automation creation
process.

• CBTA is still not perfect and contains some bugs (e.g. IF statement). There is still room
for improvement.

• Manual interventions are required for more complex scenarios using VB Scripting

• A strong technical understanding of SAP’s functionality is required to build test scripts.

This includes also a deep understanding of the expected outcomes.

18
NZSUG – May 2015
Questions

© 2015. For information, contact Deloitte Touche Tohmatsu Limited. 19

© 2013 Deloitte