Inter Sting SAP Testing

8/6/2019 Inter Sting SAP Testing

1/55

Automatic test automation Automatic test automationWhat we do, how far we got, and where do we want to go


2/55

2

Agenda Agenda

Our original target

SAP Tools or non SAP tools for testautomation

Fully automatic test of business processes

How far did we manage

Fully automatic test of output management

Perspectives


3/55

3

Agenda Agenda

Our original target





Perspectives


4/55

4

Targets: TestautomationTargets: Testautomation

Testautomation of the essential business processes in order to confirm thecorrect functionality of the software

to simulate the essential business processes covered by the softwareto apply fully automatic tests of very complex business processesto significantly reduce staff required for the manual testShorter lead times, optimizing the use of available testing ressourcesPrecise repeatability of test scenarios across multiple releases

Testresult reliabiltyIncreased product stability and qualityIncrease the reliabilty of the test performanceIncreasing the test coverage level

Documentation of test results Automatic generation of test results documentation


5/55

5

Agenda Agenda

Our original target



H ow far did we manage


Perspectives


6/55

6

How far did we manageHow far did we manage

Testautomation of the essential business processes in order to confirm thecorrect functionality of the software

to simulate the essential business processes covered by the softwareto apply fully automatic tests of very complex business processes

to significantly reduce staff required for the manual testShorter lead times, optimizing the use of available testing ressourcesPrecise repeatability of test scenarios across multiple releases

Testresult reliabiltyIncreased product stability and qualityIncrease the reliabilty of the test performanceIncreasing the test coverage level

Documentation of test results Automatic generation of test results documentation


7/55

7

How far did we manageHow far did we manage-- the essentialsthe essentials

We had to find solutions to these problems:B usiness processes do not pay attention to the input methods of thesoftware

- Some of these input methods are not supported by eCatt ( IDOC andbatch processing)

In order to achieve fully automatic regression tests we must find a way toproduce test data dynamically without human interference

In order to achieve absolute test result reliability, we had to find a way toremove factors which would reduce the sharpness of the test processes

The complicated and complex business processes consist of a largenumber of steps which need to be performed in a controlled sequence andto exchange parameters in a controlled and secure manner


8/55

8

How far did we manageHow far did we manageinput methodsinput methods

Examples of test processes with various input methods

Dialogue normal online user transaction easily supported by eCatt

B atchprocess Dunning ( occasionally with a user interface to type in the information tobe processed but the processing itself is batch and asynchronous

Creation and processing of input files

Creation and processing of IDOC files

Automatic database inspection checks


9/55

9

How far did we manageHow far did we manageDynamic supply of test dataDynamic supply of test data

Some trivial test data problems

Which date do I need for this dunning test proces?Which date is it in two months?

How do I know if this person has already been inserted into the systemHow do I know, which date it is in 20 days also if it needs to be a bank day


10/55

10

How far did we manageHow far did we managetest result reliabilitytest result reliability

How to reach test reliability:

Y ou need to know everything about the test dataHow old it is

Which attributes it hasEach and every attributeEach and every connection or link to other data elements


11/55

11

How far did we manageHow far did we managecomplex business processescomplex business processes

The means of referenced eCatt scripts does not offer a configurativeflexibility

The referenced eCatt scripts would not be the right means for the input

methods which can not be processed with eCatt


12/55

12

How far did we manageHow far did we manageRequirementsRequirements - - summarysummary

If you want to control your test process, you must create and process allrequired data yourself. Y ou cannot rely on the quality of data already inthe system.

You need to be able to produce valid test data automatically and supplythis test data also automatically to your test process.

Y ou need to be able to service different kind of input methods in order to be able to offer test of entire business processes.

If you want to provide a fully automatic test service you must focus onrelatively low maintenance.


13/55

13

How far did we manageHow far did we manageSolutionSolution head lineshead lines

Our test processes generate and, where required, process their testdata themselves.

Our test processes support different input methods.

The steps of our test processes are linked together and exchangeparameters through configurations (rather simple table entries).

Due to the configuration ability we concentrate our maintenance onchanges in the software products which we test.


14/55


15/55

15

Agenda Agenda

Our original target


F ully automatic test of business processes



Perspectives


16/55

16

Fully automatic test of business processesFully automatic test of business processesB asic exampleB asic example

One testprocess contains several test stepsThe steps of the testprocess are linked together through table entriesEach test step produces parametersThese parameters can be picked and processed up by succeeding steps

The test steps are also supplied with test data from the standard eCatt testdata container


17/55

17

Fully automatic test of business processesFully automatic test of business processesTestprocessesTestprocesses Monitoring overviewMonitoring overview


18/55

18

Fully automatic test of business processesFully automatic test of business processestestprocesstestprocess test stepstest steps


19/55

19

Fully automatic test of business processesFully automatic test of business processestestprocesstestprocess test stepstest steps


20/55

20

Fully automatic test of business processesFully automatic test of business processestestprocesstestprocess test parameters and valuestest parameters and values


21/55

21

FullyFully automatic test of business processesautomatic test of business processesThe parameters are picked up by suceeding stepsThe parameters are picked up by suceeding steps


22/55

22

Fully automatic test of business processesFully automatic test of business processesSome examplesSome examples screen shotsscreen shots

To minimize maintenance efforts, it is very important, to create the test scriptsas modular as possible. For example, there is the business partner dialogue;in oscare , there are 39 different roles for bps and according to most of them,the dialogue is different, mainly concerning the number of tab strips, whichones are to process and their order.

Hereinafter two examples are shown by screenshots, at first a school and thenan employer are created.


23/55

Fully automatic test of business processesFully automatic test of business processesCreation of a school as a business partner Creation of a school as a business partner


24/55



25/55



26/55



27/55



28/55


29/55

Fully automatic test of business processesFully automatic test of business processesCreation of an employer as a business partner Creation of an employer as a business partner


30/55



31/55



32/55



33/55



34/55



35/55



36/55



37/55



38/55

38


To cover all different requirements with one script, it is neccessary, toencapsulate every tab strip within one single script. All of those scripts arereferred within a so called masterscript. The testdatacontainer is used, tomanage the process by different flags, like for example I_D O _PARTNERIN F O. If the flag is set, the relevant tab strip is processed, otherwise not.

Moreover, the same tab strips can have different positions, depending on therole. To handle that fact, a table had to be developed, where the information isstored, which tab strip can be found at what place (according to the role), whatis its name and what is its ID.


39/55

39


B elow all entries for the Partnerinfo-tab are shown:


40/55

4 0


Here the protocol entry, that was originated while choosing the Partnerinfo-tabstrip during runtime, when name and id were determined:


41/55

4 1

Agenda Agenda

Our original target




F ully automatic test of output management

Perspectives


42/55

4 2

Fully automatic test of output managementFully automatic test of output managementWhat was the problem and how it was solvedWhat was the problem and how it was solved

A precise and reliable test of the correct generation and formation of RDI andXSF files is rather problematic.

The requirements describing how these fields supposedly should bepopulated were defined and stored in testautomation.Functions to examine the correct population of the fields of these outputfiles were developed.Most of the required business processes had already been testautomated.Eventually we just had to add the output function and connect them to

the field inspection functions.


43/55

4 3

Fully automatic test of output managementFully automatic test of output managementTwo kinds of field inspectionTwo kinds of field inspection

Mainly in order to avoid loosing control of the automated output inspectionchecks we split the checks up in two categories.

Appearance checks does the output field actually occur in the outputstream?Content checks does the output field hold exactly the expected value?


44/55

44

Appearance checks Appearance checksRDIRDI

Target: Do all required fields occurr?Did unexpected fields occurr?

H ow it works:We test automate the businessprocessThe steps of the businessprocess populate the datafields, which should eventuallyshow up in the output streams.The OPM field documentationof the data streams istransferred to a simple R/3tableThe appearance checks areappended to the business andprint part process

OPM checks

Business

process

P rinting part


45/55


46/55

4 6

Content ChecksContent ChecksH ow it worksH ow it works

The content check contains two components

Ex traction of the e xpected field contentConfiguration table entries set up exactly from which teststeps, exactly whichparameter the expected content of this output field holds.

The function that extracts the expected field content reads these configuration entriesand picks out the parameter values.

Comparison - e xpected with actual output stream fieldsThis function compares the expected field content with the actual stream fields.


47/55

4 7

Content CheckContent Check

OPM checks

Businessprocess

P rint part


48/55

4 8

Content ChecksContent Checks

Ex traction of e xpected values


49/55

4 9

Content chekcsContent chekcs

Comparison e xpected - actual


50/55

5 0

Agenda Agenda

Our original target





P erspectives


51/55


52/55

5 2

Agenda Agenda

Our original target

S AP Tools or non S AP tools for testautomation




Perspectives


53/55

5 3

S AP -EcattS AP native free to use toolVery integrated automation capabilities and interfaces

No serious support of non S AP GU I DialoguesTosca

Acquisition and / or licensing costs

Videocam- TechnologyF ilms everything also W EB dialogues (understands nothing)No S AP -IntegrationNo S AP InterfacesVery limited (if at all available) test result checks

Compuware und MercuryH igh priced and licensing costs

F ilms everything also W EB dialogues (understands nothing )

No S AP -IntegrationNo S AP Interfaces

Very limited (if at all available) test result checks

S AP or non S AP tools for testautomation


54/55


55/55

55

eCATT or different SAP tools for testautomation?eCATT or different SAP tools for testautomation?

Supported protocols :SAP GUIWebDynproJava

Web, SAP-Web (Portal)Win32.NETTerminal (3270, 5250)Power B uilder Oracle Forms, Oracle Applications, Siebel,PeopleSoftMS Office, V B , Visual Age

License costs : depends

S AP Quick Test P rofessional by H P

Supported protocols:SAP GUIWebDynpro JavaWebDynpro A B AP (only selected objects)

SAP Web ServicesLicense costs: none

S AP eC ATT

Documents

Inter Sting SAP Testing