eCATT

Unit 1: Getting Ready to Test With eCATT

Unit Objectives
In this unit, you will learn:
How a finished eCATT test case is put together The different object types used in eCATT How to set up a system for use with eCATT Some of the security aspects that you need to consider

SAP AG 2003, PDECAT 2003/2, JM/ 3

A Finished Example
Test Configuration

System Landscape Description

Test Instructions

Data to drive the test

Archive
Results

SAP AG 2003, PDECAT 2003/2, JM/ 4

The Different Object Types

Test Script
The set of commands that forms the test

System Data Container

A list of systems that are addressed during the execution of a test script

Test Data Container

Reusable sets of data that can be used to run tests

Test Configuration
A test script, combined with data from one or more test data containers, plus a system data container that describes the correct system landscape
SAP AG 2003, PDECAT 2003/2, JM/ 5

Mapping the System Landscape

1. 2. eCATT 3. 4.

Web AS 6.20

Test CRM transaction Check table entries in R/3 Run transaction in R/3 Call function module in APO

RFC

CRM

R/3

APO

Business Process
SAP AG 2003, PDECAT 2003/2, JM/ 6

Defining RFC Destinations

Source System
RFC Destination Client: Lang: User: Pwd: 100 EN tester letmein

Target System

Direct but unsafe

Target Transaction

Safe but cannot run unattended

RFC Destination
Client: 100 Lang: EN User: <current> Target Transaction

SAP AG 2003, PDECAT 2003/2, JM/ 7

Function of System Data Containers

Test Script System Data Container Command With Logical Target Target System

Target < -- > RFC Dest.

The logical target describes the function of the system for example R/3. The system data container maps the logical name to a particular RFC destination.

SAP AG 2003, PDECAT 2003/2, JM/ 8

Creating a System Data Container

SAP Web AS 6.20

System under test

Relationship described by RFC destination XYZ

Target system

. . .

RFC Destination XYZ

. . .

R3

System Data Container

SAP AG 2003, PDECAT 2003/2, JM/ 9

Advantages of System Data Containers

Consistency
One container can serve a whole project The RFC destinations can contain the client, language, and user name for the logon eliminates sources of errors Access to SM59 and the authorization to create system data containers can be restricted to project leads

Reuse
Using logical system names in a script means that the execution environment of the script can be changed by switching system data containers. Changes in the script coding are not required.

SAP AG 2003, PDECAT 2003/2, JM/ 10

Unit Summary
In this unit, you have learned
The different object types with which you work in eCATT How these object types support you in the various stages of planning an automated test project How to set up a system to enable eCATT How to define secure RFC destinations How to create a system data container

SAP AG 2003, PDECAT 2003/2, JM/ 11

Unit 2: eCATT Scripts and the Script Editor

Unit Objectives
In this unit you will learn:
The structure of an eCATT script The essential features of the eCATT script editor The main aspects of the eCATT scripting language How to work with parameters

SAP AG 2003, PDECAT 2003/2, JM/ 13

Design Considerations for a Script

Definite Goal
Before you write your script, work out exactly what you want it to do

Reusability
Try to create small self-contained script modules. This will make them more easily reusable.

SAP AG 2003, PDECAT 2003/2, JM/ 14

Structure of a Script

Test Script
Attributes
Parameters Importing

Exporting
Local variables

Commands

SAP AG 2003, PDECAT 2003/2, JM/ 15

Script Attributes

Administrative data about the script

Search terms: Can be used in Infosystem

Attaches system data container to script, allowing access to other systems

SAP AG 2003, PDECAT 2003/2, JM/ 16

The Script Editor

Parameter List

Command Editor

Structure Editor

SAP AG 2003, PDECAT 2003/2, JM/ 17

Simple Parameters
Creation

Use I_IMPORT = 'LH'. CHEVAR ( I_IMPORT <> 'UA' ). . . .

SAP AG 2003, PDECAT 2003/2, JM/ 18

Structured Parameters

Use I_STRUCTURE-CARRID = 'LH'.

I_ITAB[2]-CONNID = '0400'.
GETLEN ( I_ITAB, VAR ).

SAP AG 2003, PDECAT 2003/2, JM/ 19

Script Language

Recording and playback of applications

Conditions

Checks

Loops

Calculations

Simulation of Customizing settings

Reading table values

Blocks of ABAP coding

SAP AG 2003, PDECAT 2003/2, JM/ 20

Commands for Recording Applications

Recording and playback of applications

FUN calls a function module TCD allows you to record and replay SAP transactions SAPGUI allows you to record sequences of screens containing controls

An interface allows you to integrate test tools from third-party vendors with SAP eCATT

SAP AG 2003, PDECAT 2003/2, JM/ 21

Choosing the Right Driver

Is the application a function module or BAPI?

No

Does the application run under SAP GUI for Windows or Java?

No

Use ext. tool

Yes

Yes Does the application use controls?

Use FUN

No

Use TCD
No

Yes

No single driver provides the best solution for every application

SAP AG 2003, PDECAT 2003/2, JM/ 22

Are the controls essential within the transaction? Yes

Use SAPGUI

Special Variables
&SZBRC - Return code &TIME - Current time &DATE Current date &YEAR Current year &YEARA Next year &YEARB Last year &LPC Loop counter &MSX Number of messages returned by a transaction

&USER User name

&CLIENT Current client

SAP AG 2003, PDECAT 2003/2, JM/ 23

Pattern Function
The Pattern function is similar to the statement pattern in the ABAP Editor. It allows you to build individual eCATT commands. A command consists of:
The command keyword Argument (the target object) Interface (parameters that need to be passed) Target system

SAP AG 2003, PDECAT 2003/2, JM/ 24

Command Interface
Most eCATT commands have a command interface, which corresponds to:
The interface of a function module (for FUN) The screen and field structure of a transaction (for TCD) A list of user interactions (for SAPGUI) The importing and exporting parameters of a referenced script

Command interfaces are stored in XML format in the local system, even if the object that they describe only exists in a remote system.

SAP AG 2003, PDECAT 2003/2, JM/ 25

Unit Summary
In this unit, you have learned
The various areas of the eCATT Test Script Editor The features of the eCATT script language How to create eCATT parameters How to use the pattern function in the eCATT Script Editor Which driver to use for various kinds of applications

SAP AG 2003, PDECAT 2003/2, JM/ 26

Unit 3: Non-UI Testing

Function Modules and BAPIs Table Operations Inline ABAP

Unit Objectives
In this unit you will learn:
How to test function modules and BAPIs How to read from and test against the database How to use blocks of ABAP coding to enhance your test scripts

SAP AG 2003, PDECAT 2003/2, JM/ 28

Choosing the Right Driver

Is the application a function module or BAPI?

Yes

Use FUN

SAP AG 2003, PDECAT 2003/2, JM/ 29

Non-UI Testing: Function Modules

Unit Test Function Module Whole Backend Process Function Module Utility Within a Script

Transaction

Function Module

Function Module

Function Module

Transaction

SAP AG 2003, PDECAT 2003/2, JM/ 30

Testing Function Modules

FUN ( <function module>, <interface>, [<target>] ).

Command Interface

Importing

Exporting Changing
Tables

Function Module

Exceptions

SAP AG 2003, PDECAT 2003/2, JM/ 31

Parameterizing the Interface

or
INTERFACE-IMPORTING-PARAMETERNAME = value. INTERFACE-IMPORTING-STRUCTURE-FIELDNAME = value. INTERFACE-TABLES-TABLE[idx]-FIELDNAME = value.

SAP AG 2003, PDECAT 2003/2, JM/ 32

Trapping Exceptions

Interface
Exceptions DATA_INCOMPLETE CREATE_FAILED

Interface
Exceptions
DATA_INCOMPLETE CREATE_FAILED

SAP AG 2003, PDECAT 2003/2, JM/ 33

Table Operations

Test Script
GETTAB ( TAB, INTF, [DEST] ). CHETAB ( TAB, INTF, [DEST] ). SETTAB ( TAB, INTF, [DEST] ). RESTAB ( TAB, [DEST] ).

Database

Application Table

Customizing Table

SAP AG 2003, PDECAT 2003/2, JM/ 34

Using Inline ABAP

ABAP. * Any ABAP Coding that is allowed in a subroutine * may appear here ENDABAP.

Parameters Name Description

V_TAB SFLIGHT-table

Value <INITIAL>

I/E/V V

Ref Type SFLIGHT[]

ABAP. SELECT * FROM sflight INTO TABLE v_tab WHERE carrid = LH AND connid = 0400. ENDABAP.
Expecting a result set of more than one line. No corresponding function module available. Once-off query
SAP AG 2003, PDECAT 2003/2, JM/ 35

Unit Summary
In this unit you have learned:
How to test function modules and BAPIs How to read from and test against the database How to use blocks of ABAP coding to enhance your test scripts

SAP AG 2003, PDECAT 2003/2, JM/ 36

Unit 4: Testing Transactions - I

Testing conventional transactions using the TCD command

Unit Objectives
In this unit you will learn:
What transactions are suitable for testing using the TCD command How to record a transaction using the TCD command How to set input fields, read output fields, and perform fields checks with the TCD command

SAP AG 2003, PDECAT 2003/2, JM/ 38

Choosing the Right Driver

Is the application a function module or BAPI?

No

Does the application run under SAP GUI for Windows or Java?

Yes Does the application use controls?

No

Use TCD
No

Yes Are the controls essential within the transaction?

SAP AG 2003, PDECAT 2003/2, JM/ 39

Characteristics of the TCD Command

The TCD command is the recording technique that was used to test transactions in CATT It is based on the Batch Input Interface

It allows you to record a transaction, parameterize its input fields, and read or set checks against its output fields

SAP AG 2003, PDECAT 2003/2, JM/ 40

Background: The Batch Input Interface

Background: Data-consistency checks in SAP transactions are often implemented within the coding of the screen flow logic (Process After Input)

Batch Input is a technique originally developed for data transfer from legacy systems into an R/3 System that processes transactions in the background

CATT used this technique for unattended transaction testing. It is a very efficient testing method, and has consequently been retained in eCATT

SAP AG 2003, PDECAT 2003/2, JM/ 41

The TCD Command

TCD ( transaction, interface, [sys] )

Same system

Different system

SAP AG 2003, PDECAT 2003/2, JM/ 42

How TCD Really Works - Recording

ENTER

FIELD VBAK-AUART VBAK-VKORG . . . BDC_OKCODE

VALUE AF 1000 ENT2

FIELD KUAGV-KUNNR VBAP-MATNR . . . BDC_OKCODE

VALUE 1280 P-103 SICH

SAP AG 2003, PDECAT 2003/2, JM/ 43

How TCD Really Works - Replay

No SAP GUI session

Field values FIELD VBAK-AUART VBAK-VKORG . . . BDC_OKCODE VALUE AF 1000 ENT2 Function code FIELD KUAGV-KUNNR VBAP-MATNR . . . BDC_OKCODE VALUE 1280 P-103 SICH

SAP AG 2003, PDECAT 2003/2, JM/ 44

The Command Interface

Transaction

Screen Field Field Field Screen

Field

Field

SAP AG 2003, PDECAT 2003/2, JM/ 45

Parameterizing Input Fields

You can replace the recorded values with either literals or variables
Field name Double-click Value

SAP AG 2003, PDECAT 2003/2, JM/ 46

Reading and Checking Output Fields

To... MODE must be... Field name in VALIN column Will contain value from output field at the end of the transaction Contains the value that must be present in the screen field at runtime

Read a value

'G' 'C'

Check a value

SAP AG 2003, PDECAT 2003/2, JM/ 47

Message Handling

TCD Command Interface

Location of message
(program and screen)

Message attributes

MSG
Internal Table

(type, ID, number)

Message variables
(up to four)

Number of messages &MSX

Full text of message

(in logon language)

SAP AG 2003, PDECAT 2003/2, JM/ 48

Reading Message Contents

Addressing the Last Message <interface>-MSG[&MSX]-<component>

Looping Through All Messages DO &MSX. <interface>-MSG[&LPC]-<component> ENDDO.

SAP AG 2003, PDECAT 2003/2, JM/ 49

Testing Messages

Require that a particular message is sent ON_LAST_MESSAGE_CHECK ( 031 ). TCD ( EC_TUTORIAL_TCD, EC_TUTORIAL_TCD_1 ).

Tolerate all messages ON_LAST_MESSAGE_CHECK ( * ). TCD ( EC_TUTORIAL_TCD, EC_TUTORIAL_TCD_1 ).

SAP AG 2003, PDECAT 2003/2, JM/ 50

Troubleshooting the TCD Command

SAP AG 2003, PDECAT 2003/2, JM/ 51

Unit Summary
In this unit you have learned:
What transactions are suitable for testing using the TCD command How to record a transaction using the TCD command How to set input fields, read output fields, and perform fields checks with the TCD command

SAP AG 2003, PDECAT 2003/2, JM/ 52

Unit 5: Testing Transactions - II

Testing control-based transactions using the SAPGUI command

Unit Objectives
In this unit, you will learn:
Why the TCD driver is not suitable for testing all transaction types How GUI Scripting works How to use the eCATT SAPGUI command to record a transaction How to set input fields, read output fields, and perform field checks in a SAPGUI recording

SAP AG 2003, PDECAT 2003/2, JM/ 54

Choosing the Right Driver

Is the application a function module or BAPI?

No

Does the application run under SAP GUI for Windows or Java?

Yes Does the application use controls?

Yes Are the controls essential within the transaction? Yes

Use SAPGUI
SAP AG 2003, PDECAT 2003/2, JM/ 55

Why TCD Cannot Test Everything

SAP GUI Window Control
ALV Tree Calendar New recording component OCX control under Windows Bean under Java Action leads to local processing in SAP GUI

Frontend

Backend

TCD Recorder
eCATT Application Logic

Action leads to event handler on application server

SAP AG 2003, PDECAT 2003/2, JM/ 56

Introducing GUI Scripting

Scripting host in GUI (Requires SAP GUI 6.20)

eCATT at backend

SAP AG 2003, PDECAT 2003/2, JM/ 57

Recording the SAPGUI Command Procedure

1. Select SAPGUI(Record)

2. Set the scripting granularity

SAP AG 2003, PDECAT 2003/2, JM/ 58

Recording the SAPGUI Command - Procedure

3. Confirm that you want to record

4. Pick the relevant initial states to record

SAP AG 2003, PDECAT 2003/2, JM/ 59

Scripting Granularity

Session (potentially multiple transactions)

Transaction
Screen Separate Command Separate Command

Screen

Separate Command One Command Transaction

Screen

Separate Command

Separate Command

Screen

Separate Command

SAP AG 2003, PDECAT 2003/2, JM/ 60

Making Sense of the Command Interface - 1

One ProcessedScreen node per screen

UserChangedState describes the user actions on the screen

SAP AG 2003, PDECAT 2003/2, JM/ 61

Parameterizing an Input Value

Field name

Enter parameter name in this field

Double-click

SAP AG 2003, PDECAT 2003/2, JM/ 62

Recording the SAPGUI Command Initial State

SAP AG 2003, PDECAT 2003/2, JM/ 63

Active and Inactive Checks

Active Checks
Record the initial states of the selected screen element types On replay, check that the values in the fields correspond to the recorded initial states

Inactive Checks
Record the initial states of the selected screen element types so that they can be placed into script parameters and used in the rest of the script

SAP AG 2003, PDECAT 2003/2, JM/ 64

Making Sense of the Command Interface - 2

One InitialState node per processed screen Are checks active?

Field name

Field value during recording

SAP AG 2003, PDECAT 2003/2, JM/ 65

Retrieving an Output Value

Double-click

Enter parameter name in this field

SAP AG 2003, PDECAT 2003/2, JM/ 66

Activating and Deactivating Field Checks

SAP AG 2003, PDECAT 2003/2, JM/ 67

Message Handling MESSAGE

Stipulate that certain messages must/must not occur in order for the script to be a success

Find out what messages occurred during a particular block of SAPGUI commands

SAP AG 2003, PDECAT 2003/2, JM/ 68

Message Handling - ENDMESSAGE

MIDX <n> 2 3 MODE F A A MSGTYP E E S MSGID ECDEMO ECDEMO XY MSGNR 003 021 100 MSGV1 LH MSGV2 0400 MSGV3 MSGV4

E_MSG_1

E_MSG_1[1]-MIDX contains the total number of messages in the table

SAP AG 2003, PDECAT 2003/2, JM/ 69

Creating Rules in the MESSAGE Statement

Rule = What to do + Message qualification

What to do R: E: A: F: Require Expect Allow Fail

Message qualification
Message Type Message Class

Mode

Any combination of Continue processing or jump directly to ENDMESSAGE?

Exit

Message Number

SAP AG 2003, PDECAT 2003/2, JM/ 70

Some Sample Message Rules

Tolerate all error messages

Mode 'A'

Exit

MSGTYP 'E'

ID

Number

Fail script and jump to ENDMESSAGE on error message ZJM 001

Mode 'F'

Exit 'X'

MSGTYP 'E'

ID Number 'ZJM' '001'

SAP AG 2003, PDECAT 2003/2, JM/ 71

Default Message Handling Rules

User-defined Rules

Allow

Success Information messages Warning

Fail and Exit

Error Termination messages Dump

SAP AG 2003, PDECAT 2003/2, JM/ 72

Message Processing

Look up in user-defined rules New Message

Look up in default rules

Discard

Process according to rule

SAP AG 2003, PDECAT 2003/2, JM/ 73

Process according to rule

The SAPGUI Command Interface 4

System Information

SAP AG 2003, PDECAT 2003/2, JM/ 74

Activating and Deactivating Screens

Active = X: Screen active Active = : Screen inactive Active = O: Screen optional

Screen 1

Screen 2

Screen 3

Join OK?
SAP AG 2003, PDECAT 2003/2, JM/ 75

Troubleshooting in the SAPGUI Command

Set automation queue behavior

Run commands with stops at various granularity levels

Close GUI sessions or leave them open for inspection

SAP AG 2003, PDECAT 2003/2, JM/ 76

Unit Summary
In this unit, you learned:
Why the TCD driver is not suitable for testing all transaction types How GUI Scripting works How to use the eCATT SAPGUI command to record a transaction How to set input fields, read output fields, and perform field checks in a SAPGUI recording How to activate and inactivate screens in a script, and the things that you have to consider when doing so

SAP AG 2003, PDECAT 2003/2, JM/ 77

Unit 6: Testing Transactions - III

Testing Web- and Desktop-based Applications Using an External Tool

Unit Objectives
In this unit, you will learn:
When to use TCD and SAPGUI, and when you have to use an external tool Why SAP chose to work with external tools The advantages of the external tool integration How the integration works

SAP AG 2003, PDECAT 2003/2, JM/ 79

Choosing the Right Driver

Is the application a function module or BAPI?

No

Does the application run under SAP GUI for Windows or Java?

No

Use ext. tool

SAP AG 2003, PDECAT 2003/2, JM/ 80

Configuring The System for an External Tool

Run function module SET_EXTERNAL_TOOL in test mode

Run program ECATT_GENERATE_ET_USER to generate service user

Regenerate authorizations in role SAP_ECET

SAP AG 2003, PDECAT 2003/2, JM/ 81

External Tool Integration - Architecture

Application Server Database

eCATT
Script with Attributes

Scripts stored in SAP database

Frontend

Physical script commands

Application Under Test

External Tool
SAP AG 2003, PDECAT 2003/2, JM/ 82

Using Compuware TestPartner to Record a Script

Checks

VBA Functionality

Parameterization

Recording

SAP AG 2003, PDECAT 2003/2, JM/ 83

Passing Arguments To and From TestPartner Argument Container

eCATT

Argument Container

Script TestPartner
SAP AG 2003, PDECAT 2003/2, JM/ 84

Passing Arguments To and From TestPartner Script Coding

Argument Container

Name I_Name E_Value

Sub Main ()

Type String String

Direction IMPORT IMPORT

... ... ...

Dim ImportParam As String, ExportParam As String ImportParam = GetEcattArg("I_NAME") . . .

SetEcattArg "E_VALUE", ExportParam

End Sub Script: VBA Coding
SAP AG 2003, PDECAT 2003/2, JM/ 85

Uploading Scripts
Projects for upload

Script name and version

Administrative settings

SAP AG 2003, PDECAT 2003/2, JM/ 86

Calling External Scripts

REFEXT ( SCRIPT, INTERFACE, VERSION ).

SAP AG 2003, PDECAT 2003/2, JM/ 87

Unit Summary
In this unit, you have learned:
When to use TCD and SAPGUI, and when you have to use an external tool Why SAP chose to work with external tools The advantages of the external tool integration How the integration works

SAP AG 2003, PDECAT 2003/2, JM/ 88

eCATT: New Features in Release 6.40

Major New Features At-A-Glance

Web Dynpro Testing ABAP Objects Framework BC Set Integration External Variants Script Debugger

SAP AG 2003, PDECAT 2003/2, JM/ 90

Other New Features

Where-Used List Integration into SE80 Extended Syntax Check

SAP AG 2003, PDECAT 2003/2, JM/ 91

Major Improvements to Existing Features

Improved SAPGUI Handling Versioning Enhancements Usability Improvements

SAP AG 2003, PDECAT 2003/2, JM/ 92

WebDynpro Recording an Application

Use the Pattern Function

http://p12345:50000/ webdynpro/dispatcher/ local/Welcome/WelcomeApplication

For name-value pairs in URL: ?name1=value1&name2=value2

SAP AG 2003, PDECAT 2003/2, JM/ 93

RFC Destinations
Application URL http://<Target Host>:<Service No.>/<URL Extension>/<Application>
ABAP Stack: Connection Type H Java Stack: Connection Type G

Use the HTTP Destination field in the system data container

SAP AG 2003, PDECAT 2003/2, JM/ 94

Parameterizing Fields
Read values under SCREEN nodes Check values under SCREEN nodes Set values under:
DATACHANGES nodes ACTIONS nodes

Getting and checking can be done using the context menu or simulator

SAP AG 2003, PDECAT 2003/2, JM/ 95

The Command Interface

SAP AG 2003, PDECAT 2003/2, JM/ 96

Simulation and Replay

SAP GUI 6.40 required for:
simulator foreground replay

Start Options
Background Foreground

Parallel display of recorded and actual screens

Error mode starts and background and only changes to foreground in case of error

SAP AG 2003, PDECAT 2003/2, JM/ 97

ABAP Objects
New Commands in Release 6.40 For Public Static Members
CALLSTATIC ( <CLASS>, <STATIC METHOD>, <COMMAND INTERFACE>). GETSTATIC ( <CLASS>, <STATIC ATTRIBUTE>, <PARAMETER> ).

SETSTATIC ( <CLASS>, <STATIC ATTRIBUTE>, <PARAMETER> ). CHESTATIC ( <CLASS>, <STATIC ATTRIBUTE>, <PARAMETER> ).

For Public Instance Members

CREATEOBJ ( <OBJECT REF>, <CONSTRUCTOR INTERFACE> ). CALLMETHOD ( <OBJECT REF>, <INSTANCE METHOD>, <INTERFACE> ).

GETATTR ( <OBJECT REF>, <INSTANCE ATTRIBUTE>, <PARAMETER> ).

SETATTR ( <OBJECT REF>, <INSTANCE ATTRIBUTE>, <PARAMETER> ). CHEATTR ( <OBJECT REF>, <INSTANCE ATTRIBUTE>, <PARAMETER> ).
SAP AG 2003, PDECAT 2003/2, JM/ 98

External Variants
The contents of a test data container or test configuration can be downloaded as a text file (XML format also planned) External data can be uploaded from external files into test data containers or test configurations It is also possible for a test configuration or test data container not to contain any internal variants, but to point to a text or XML file on the frontend, from which the variants are read dynamically at runtime

SAP AG 2003, PDECAT 2003/2, JM/ 99

External Variants Upload

Test Configuration

Upload variants

Text File

Execute

SAP AG 2003, PDECAT 2003/2, JM/ 100

External Variants Dynamic Loading

Test Configuration

Execute
Start Options Use external variants Confirm path to variants

Upload variants

Text File

SAP AG 2003, PDECAT 2003/2, JM/ 101

Integrating BC Sets With Test Scripts

In Release 6.40, eCATT allows you to integrate BC Sets. The following BC Set activities are allowed:
Activate Simulate Activation Compare BC Set contents with currently-active Customizing settings Check that a BC Set exists in a particular system

SAP AG 2003, PDECAT 2003/2, JM/ 102

Integrating BC Sets and eCATT - Architecture

BC Set Original

Transport

BC Set Copy

DEV

Any Release from 4.6C Central eCATT Test System

QAS

Develop and test test case

Activate BC Set Run Test

CTS
Web AS 6.40
SAP AG 2003, PDECAT 2003/2, JM/ 103

The eCATT BCSET Command

BCSET ( BCSET, INTERFACE, [TARGETSYSTEM]).

Action A Activate S Simulate Activation C Compare

Change Requests Workbench Request Customizing Request

Variables

Variable parameters from the BC Set definition

E Check existence

SAP AG 2003, PDECAT 2003/2, JM/ 104

Script Debugger Based on the Log Structure

New breakpoint

Step into/over, Return, Continue

Executed commands

Current command

Parameter List
SAP AG 2003, PDECAT 2003/2, JM/ 105

Script-Wide Search
A script-wide search function (Ctrl + F)

SAP AG 2003, PDECAT 2003/2, JM/ 106

Where-Used List - Search

You can use the where-used list function for any eCATT object. The search can include any or all of the eCATT object types in which the required object can be used

SAP AG 2003, PDECAT 2003/2, JM/ 107

Where-Used List Hit List

From the hit list, you can navigate to any listed object

SAP AG 2003, PDECAT 2003/2, JM/ 108

SE80 Integration
There are two new views within the Object Navigator:

The Object Navigator shows you the test objects that belong to a particular package

The Test Repository shows you the test objects that belong to a particular application component

SAP AG 2003, PDECAT 2003/2, JM/ 109

Extended Syntax Check

Check the syntax of your inline ABAP using the Extended Syntax Check

SAP AG 2003, PDECAT 2003/2, JM/ 110

Extended MESSAGE Handling

MESSAGE command handling now applies not only to the SAPGUI command, but also to TCD, FUN, and inline ABAP The MESSAGE command can also interpret messages that are output by the application log

SAP AG 2003, PDECAT 2003/2, JM/ 111

Versioning Enhancements
A new graphical tool for managing the validity of all script versions centrally Choose Utilities -> Version Management -> Display | Change from transaction SECATT Features:
Overview of all versions of a script Maintain validity

Set Backup flag Simulation of version determination on the basis of a given target system

SAP AG 2003, PDECAT 2003/2, JM/ 112

Versioning Enhancements

SAP AG 2003, PDECAT 2003/2, JM/ 113

Usability Improvements 1
Automatic parameter creation
When you enter an undeclared parameter name in a command interface, eCATT asks you if you want it to be created

Advanced drag and drop features

Parameters from parameter list into command interfaces Command interface into editor in properly-resolved form

Copying of parameters and/or command interfaces Edit -> Parameter/Command Interfaces-> Import
From one script to another From a script to a test data container From a test data container to a script

SAP AG 2003, PDECAT 2003/2, JM/ 114

Usability Improvements - 2
Automatic Test Configuration Creation Utilities -> Test Configuration -> Create
Creates a new configuration based on the current script and system data container

Edit Command Right mouse-click on a command, choose Edit

Allows you to change arguments of a command The options that are available depend on the command

Simplified Views in Structure Editor icon in the structure editor toolbar

Reduced views of certain command interfaces to aid usability

SAP AG 2003, PDECAT 2003/2, JM/ 115

GUI Scripting New Security Features

As well as the profile parameter sapgui/user_scripting, the following two parameters provide more refined access control: sapgui/user_scripting_disable_recording
If this parameter is set to TRUE, scripts can be replayed against the system in question, but recording is not allowed

sapgui/user_scripting_set_readonly
If this parameter is set to TRUE, scripts can only contain read-only operations

SAPGUI 6.40 or 6.20 patch 42+ is required

SAP AG 2003, PDECAT 2003/2, JM/ 116

Improved SAPGUI Handling InitialState Replaced

In Release 6.40, it is no longer necessary to record the Initial States of elements in order to access output values of fields for retrieval or checking Note: Initial State recording and processing is still possible to ensure the compatibility of scripts recorded in Release 6.20

SAP AG 2003, PDECAT 2003/2, JM/ 117

GETGUI and CHEGUI - Capturing

Point and click at field in application under test

Select relevant attributes, choose insert
SAP AG 2003, PDECAT 2003/2, JM/ 118

GETGUI and CHEGUI Parameterizing

Double-click

Enter parameter name

CHEGUI allows you to perform a check against a certain value as well as retrieving the actual value in the field at runtime

SAP AG 2003, PDECAT 2003/2, JM/ 119

Improved SAPGUI Handling - SAPGUI (Attach)

When recording with SAPGUI, it is no longer necessary to open a new window each time you want to record Instead, you can attach to a window that is already open by choosing the SAPGUI (Attach) option in the command pattern dialog box

SAP AG 2003, PDECAT 2003/2, JM/ 120

Improved SAPGUI Handling SAPGUI (Attach)

You will be presented with a list of all open sessions belonging to systems on which GUI Scripting is enabled

SAP AG 2003, PDECAT 2003/2, JM/ 121

Improved SAPGUI Handling Split and Join

You can split a SAPGUI command into a number of commands of finer granularity It is also possible to join multiple SAPGUI commands in a single command

eCATT generates new command(s) and comments out the original

SAP AG 2003, PDECAT 2003/2, JM/ 122