eCATT Tutorial

eCATT Tutorial submitted by Sumeet Kaul.

eCATT- An Introduction
eCATT-Extended Computer Aided Test Tool
Introduction to eCATT.
The Extended Computer Aided Test Tool is a new automated testing tool that
allows you to create automated functional test cases for the maority of
applications running in the SA! "#I for $indows and SA! "#I for %a&a
en&ironments. 'i(e other test tools) it wor(s by ma(ing a recording of an
application) which you can then parameteri*e and replay with differing sets of
input &alues. +ou can test the beha&ior of the application by reading and testing
the &alues returned by the application . eCATT is a&ailable from ,elease -../ of
the SA! $eb Application Ser&er) and is an integral part of the mySA!
Technology underlying SA! ,01 Enterprise ,elease 2.3.
4esigned as a successor to the existing CATT) it allows a user to record and
replay any application running under SA! "#I for %a&a or SA! "#I for
$indows. 5urthermore) because it is embedded within the SA! application
ser&er) it has access to other interfaces) such as function modules) 6A!Is) or the
SA! database 7so that users can perform chec(s8) and the A6A! runtime) which
lets users write A6A! routines into test cases.
$ith SA! eCATT) users are also able to test business processes that cross
system boundaries. Each command in a test script can ha&e a separate
destination so) within one script) a user can call a transaction in mySA!
Customer ,elationship 9anagement) and also chec( table entries in an SA!
,01 system. $ithin a script) logical names are used to refer to target systems.
These logical names are mapped to actual ,5C destinations in a separate obect
called a system data container) which is) effecti&ely) a description of the
company:s system landscape. Thus by lin(ing a different system data container
with a script) a user can execute it in a completely different system landscape
without ha&ing to alter the script coding at all. The only prere;uisite is that all
the logical system names that the script uses are defined in the rele&ant system
data container.
6ecause of the wide &ariety of applications that may need to be tested) eCATT
does not ha&e a single <one-si*e-fits-all= way of recording and replaying
applications. Instead) there are &arious dri&ers that encompass the following
(inds of scenarios>
? Table operations@ interacting with the SA! database
? 5unction modules and 6A!Is
? A6A!
? Transactions and reports
? Applications running outside the SA! "#I for $indows or %a&a en&ironments

5or the last of these scenarios) eCATT offers an interface that third-party tool
manufacturers can implement to integrate their tools with eCATT.
+ou can migrate test cases from Computer Aided Test Tool 7CATT8 to ta(e
ad&antage of the better features of eCATT.
eCATT is also integrated with the Abect Ba&igator 7SEC/8.
Features
#sing eCATT we can>
? Test transactions) reports) and scenarios
? Call 6A!Is and function modules
? Test remote systems
? Chec( authori*ations 7user profiles8
? Test updates 7database) applications) "#I8
? Test the effect of changes to customi*ing settings
? Chec( system messages

Constraints
eCATT runs in a system based on SA! $eb Application Ser&er -../ or higher.
Dowe&er) you can use this system to test systems with ,elease 2.-C or higher.
In my forth coming weblog:s I will be going through the following topics >
E. Creating Test Scripts .
.. Creating Test 4ata Containers .
1. #nderstanding System 4ata Containers .
2. Executing Test Configurations .
F. #nderstanding 'ogs .
I will also demonstrate the use of eCATT with following applications>
? Testing a Standard SA! 6usiness Scenario .
? Testing a $eb 4ynpro Application .
? 9igrating Test Cases from CATT to eCATT
eCATT Tutorial
eCATT Tutorial submitted by Sumeet Kaul.
eCATT: Creating Test Scripts
#nderstanding eCATT
Creation of Test Scripts
In my last weblog on GeCATT > An Introduction= I introduced the subect of
eCATT and discussed the capabilities and features of the same . In this weblog I
will be going a step further and explain the creation of Test Scripts ) the first
step in the creation of Test Cases using eCATT .
6efore creating Test Scripts using eCATT we need to ha&e some system setting
done .
E. 9aintaining Table T///
a. Start transaction S91E.
b. In the Table/View field) enter T000.
c. Choose Maintain.
d. In the Change View Clients: Overview screen) select the rele&ant client
and choose.
e. In the Restrictions when Starting eCATT field) select an entry that allows
eCATT.
.. Enabling Scripting at the front End .
7 Chec( whether SA! "#I Scripting component is installed. There is an option
for installing this component when installing the SA! "#I.8
a. An any screen) choose Customizing o local la!out"
b. Choose O#tions....
c. Choose the Scri#ting tab.
d. Select $nable Scri#ting.
e. Choose A##l!.
1. Enabling Scripting on application ser&er .
a. Start transaction ,HEE.
b. An the Maintain %roile %arameters screen) enter sapgui/user_scripting.
c. Choose &is#la!.
d. In the &is#la! %roile %arameter Attributes screen) choose Change &alue.
e . Enter TRUE in the 'ew &alue field.

Bow we will start with creation of Test Scripts >
The first step in the Creation of Test Case is Creation of Test Scripts .
A test script consists of three principal parts-
Its attributes
The script commands
The parameters

$e will be creating a Test Scripts for Sales Arder Scenario .
StepE > "oto Transaction SECATT >
Bow the ,ecording for the Transaction IA/E will start .$e will ,ecord and
sa&e the Transaction .
After ,ecording is sa&ed TC4 Command Appears in the Command Editor.
Bow 4efine !arameters . Anly those parameters should be defined which are
expected to ta(e &alues at runtime.
An clic(ing the Toggle Aption > The Command Editor Appears .
An clic(ing the GComman( )nterace= Aption the interface appears in left
bottom corner of the screen .
5or each screen tra&ersed screen name and screen number appears . $ithin each
screen all the Input &alues that were entered during ,ecording are
parameteri*ed .
$hen all the screen input fields are parameteri*ed ) sa&e the Script .
This Creates the Test Script for the Sales Arder Scenario.
In the next $eblogs I will be discussing Test Data Containers , System Data
Containers and Test Configurations to complete the Test Case for the Sales
Arder Scenario.
eCATT Tutorial submitted by Sumeet Kaul.
eCATT: Creation of Test Data Container
Creating Test Cases using eCATT

Creation of Test Data Container .
In my last weblog we were discussing creation of Test Case for Sales Arder Scenario .
The first step for Creation of Test Case i.e. creation of Test script was co&ered in the
pre&ious weblog . In this weblog we will continue the flow and co&er Creation of G
Test Data Container= and GSstem data Container G for the Test Scenario .
Transaction JSECATT:. > Creating Test 4ata Container
Bow Create Iariants for the Test Case .
The Script will be Tested with these 1 &ariants . These Iariants define the different set
of &alues with which the Scenario will be tested . In the abo&e case the Sales Arder
Creation will be tested for different set of Sales Area 4ata 7 different distribution
channels in namely> E/ E. K E- 8
After creation of Test 4ata Container ) In the test script the parameters are assigned to
the Input &alues0Autput Ialues .
!arameteri"ing Input Fields >
+ou must set the field mode to JS:) and enter a literal or the name of a parameter in the
#A$I% column. At runtime) the screen field will be filled with the &alue that you
specified.
!arameteri"ing &utput Fields >
+ou must set the field mode to J':) and enter the name of a parameter in the #A$I%
column. At runtime) the parameter will be filled with the &alue from the screen field.
%o( Creation of Sstem data Container >
Transaction JSECATT:.
Since we are not 4oing ,emote Testing .Therefore Test System is G%&%E=
7In Case of ,emote Testing ,5C destination has to be created in S)*+ and should be
specified under G,FC Destination Ta-=8
In the next weblog Creation of GTest Configuration= and Execution of the Test Case
will be co&ered thus completing the Test Case for Sales Arder Scenario.
eCATT Tutorial
eCATT Tutorial submitted by Sumeet Kaul.
eCATT: Creating . Executing Test Configurations
Creation of Test Configuration
In my pre&ious weblogs on eCATT we were discussing GCreation of Test Case
for the Sales Arder Scenario= . In the last weblog I had demonstrated the
creation of GTest 4ata Container= . The only step left for the completion of Test
Case for the abo&e said scenario is the creation of GTest Configuration G.
I will explain creation of GTest Configuration= with the help of Screen Shots .
Transaction JSECATT: . > Creating Test Configuration .
In the Test Configuration 7 "sales_config 8 Test data G/SA$ES_DATA=7
Created in last 0e-log 8 is attached .
%ote : T1e field Target Sstem is 2lan3 as Testing (ill -e performed
$ocall .
Bow we ha&e to copy &ariants from Test 4ata Container to the Test
Configuration .
The abo&e screen shows the three &ariants namely >
L ECATT4E5A#'T
L IA,E
L IA,1
Bow the execution of this Test Configuration will Test the Sales Arder !rocess
with three different set of data .
Executing Iariants at once is &ery much possible in eCATT. 9a(e sure that the
chec( box of Close ,5C Connection is not selected otherwise for each &ariant
you will be prompted for login screen of target ,01 system.
There are following three ways of doing it -
E. "i&e nothing in Iariant field of Start Aptions window at run time. This blan(
&alue will execute all the &ariants including the eCATT4E5A#'T &ariant.
.. "i&e M in the Iariant field of Start Aptions window at run time. This will
execute all the &ariants except the ECATT4E5A#'T one.
1. "i&e the specific one &ariant) which you want to execute in &ariant field of
Start Aptions window. This will execute only the specified &ariant.
Executing Test Configuration > "sales _config .
Bow ) The 'og "enerated after /SA$ES_C&%FI' was executed .
The 'og re&eals that &ariant ECATTDEFA4$T A%D #A,5 executed
successfully 7 i.e sales order creation was possible with these set of 4ata 8
6ut with Iariant IA,1 Error > Arder type A, not defined in Sales AreaNE///
E- // occurs .
5rom the abo&e Test Scenario we were able to infer that
Standard Sales Arder type A, cannot be created in 4istribution channel E- .
Thus we ha&e successfully created a Test Case for the Sales Arder Scenario .
In my next weblog on eCATT ) I will discuss Creation of Test Case for
G0e-Dnpro= applications .
eCATT Tutorial
eCATT Tutorial submitted by Sumeet Kaul.

eCATT: Creating a Test Case for a 0e- Dnpro Application
This $eblog will discuss how to create a Test Case for a 0e- Dn!ro
Application. This is one of the maor features of eCATT that allows users to test
business processes that cross system boundaries.
In my pre&ious $elogs on eCATT ) I discussed topics starting from
<Introduction to eCATT< to <Executing a Test Case using eCATT <. This $eblog
will go a step further and discuss how to create a Test Case for a 0e- Dn!ro
Application. This is one of the maor features of eCATT that allows users to test
business processes that cross system boundaries.
The scenario for Test is as follows >
Scenario
The goal is to create a Test Case for a $eb 4ynpro Application that is on a&a
Stac( . The application is for !urchase Arder Creation.
The application will be tested for different set of data .
The url is > http>00Nser&erO>NportO0webdynpro0dispatcher0local0!A0Create!A
!rocedure:
The first step towards creating a Test Case for a $eb 4ynpro Application is to
create a
,5C destination in SA! .
Tcode > S9FP
,5C 4estination > $E64+B!,A. ) Type > "
Target Dost > Nser&erO
Ser&ice > NportO
Bow ) create a System data Container assigning DTT! ,5C destination created
abo&e .
Tcode > SECATT
After creation of Test 4ata Container ) Create Test Script . 7 the creation of the
same has been discussed at length in my pre&ious weblogs 8
In pattern option under #I control "roup select $E64+B!,A command .
Entering System data Container and Target System .
The Application in our case is G0webdynpro0dispatcher0local0!A0Create!A=
,ecording starts . The application starts in the browser .
Entering appropriate Deader Info in the fields .
Adding item details .
Creating !urchase Arder .
The !A is created in SA! and the !A number is reflected in top right corner .
Bow ) clic( GStop ,ecording= Aption .
6elow we can see a $E64+B!,A command is created for each page of
application.
Bow !arameteri*e the Input &alues
Creating Test 4ata Container .
. Iariants for are created . The Company code data is different in both cases .
5or Test Iariant E > Company Code is E///.
5or Test Iariant . > Company Code is 1///.
Bow Creating Test Configuration and attaching Test 4ata Container .
Executing Test Configuration .
Examining 'og we see that >
!A can be created with &arE 7 Company Code >E/// 8
!A cannot be created with &ar. 7 Company Code >1/// 8
Thus we were able to successfully Create a Test Case for a 60e- Dnpro
Application6 deployed on %a&a Stac( using eCATT.