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 ma ority 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 ob ect 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 Ab ect 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
Bow we will start with creation of Test Scripts > The first step in the Creation of Test Case is Creation of Test Scripts . c. e . An any screen) choose Customizing o local la!out" b. Choose O#tions. In the Table/View field) enter T000. A test script consists of three principal parts•
. 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 . There is an option for installing this component when installing the SA! "#I. Enter TRUE in the 'ew &alue field. Select $nable Scri#ting. 6efore creating Test Scripts using eCATT we need to ha&e some system setting done .8 a. Choose A##l!. An the Maintain %ro ile %arameters screen) enter sapgui/user_scripting. In the &is#la! %ro ile %arameter Attributes screen) choose Change &alue. d. Start transaction S91E. 7 Chec( whether SA! "#I Scripting component is installed. c. c.HEE. Choose the Scri#ting tab. In the Restrictions when Starting eCATT field) select an entry that allows eCATT. b.. e. Choose &is#la!.. e. .. a.. Start transaction .eCATT Tutorial eCATT Tutorial submitted by Sumeet Kaul. d. Enabling Scripting on application ser&er . E. b. d. In the Change View “Clients”: Overview screen) select the rele&ant client and choose. Choose Maintain. 1. 9aintaining Table T/// a. Enabling Scripting at the front End . eCATT: Creating Test Scripts #nderstanding eCATT Creation of Test Scripts In my last weblog on GeCATT > An Introduction= I introduced the sub ect of eCATT and discussed the capabilities and features of the same .
StepE > "oto Transaction SECATT >
The script commands The parameters
$e will be creating a Test Scripts for Sales Arder Scenario .
Bow the .
.ecord and sa&e the Transaction .ecording for the Transaction IA/E will start .$e will .
.After .ecording is sa&ed TC4 Command Appears in the Command Editor.
An clic(ing the Toggle Aption > The Command Editor Appears .Bow 4efine !arameters .
. Anly those parameters should be defined which are expected to ta(e &alues at runtime.
This Creates the Test Script for the Sales Arder Scenario.An clic(ing the GComman( )nter ace= Aption the interface appears in left bottom corner of the screen .ecording are parameteri*ed . System Data Containers and Test Configurations to complete the Test Case for the Sales Arder Scenario.
. $ithin each screen all the Input &alues that were entered during . 5or each screen tra&ersed screen name and screen number appears . $hen all the screen input fields are parameteri*ed ) sa&e the Script . In the next $eblogs I will be discussing Test Data Containers .
creation of Test script was co&ered in the pre&ious weblog . Transaction JSECATT:. In my last weblog we were discussing creation of Test Case for Sales Arder Scenario . eCATT: Creation of Test Data Container Creating Test Cases using eCATT Creation of Test Data Container .eCATT Tutorial submitted by Sumeet Kaul. > Creating Test 4ata Container
.e. In this weblog we will continue the flow and co&er Creation of G Test Data Container= and GS stem data Container G for the Test Scenario . The first step for Creation of Test Case i.
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. At runtime) the screen field will be filled with the &alue that you specified. These Iariants define the different set of &alues with which the Scenario will be tested .8 After creation of Test 4ata Container ) In the test script the parameters are assigned to the Input &alues0Autput Ialues .
The Script will be Tested with these 1 &ariants .Bow Create Iariants for the Test Case . !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. K E.
!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 S stem data Container > Transaction JSECATT:.
5C destination has to be created in S)*+ and should be specified under G.Since we are not 4oing .emote Testing .emote Testing .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.
.Therefore Test System is G%&%E= 7In Case of .
I will explain creation of GTest Configuration= with the help of Screen Shots . In the last weblog I had demonstrated the creation of GTest 4ata Container= . 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= .
. Transaction JSECATT: .eCATT Tutorial eCATT Tutorial submitted by Sumeet Kaul. The only step left for the completion of Test Case for the abo&e said scenario is the creation of GTest Configuration G. eCATT: Creating . > 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 S stem is 2lan3 as Testing (ill -e performed $ocall . Bow we ha&e to copy &ariants from Test 4ata Container to the Test Configuration .
01 system.E L IA.The abo&e screen shows the three &ariants namely > L ECATT4E5A#'T L IA.5C Connection is not selected otherwise for each &ariant you will be prompted for login screen of target .1 Bow the execution of this Test Configuration will Test the Sales Arder !rocess with three different set of data . There are following three ways of doing it E. This blan(
. 9a(e sure that the chec( box of Close . "i&e nothing in Iariant field of Start Aptions window at run time. Executing Iariants at once is &ery much possible in eCATT.
"i&e M in the Iariant field of Start Aptions window at run time.
The 'og re&eals that &ariant ECATTDEFA4$T A%D #A.e sales order creation was possible with these set of 4ata 8 6ut with Iariant IA. This will execute only the specified &ariant.. Executing Test Configuration > "sales _config . not defined in Sales AreaNE///
.1 Error > Arder type A. 1. This will execute all the &ariants except the ECATT4E5A#'T one.&alue will execute all the &ariants including the eCATT4E5A#'T &ariant. .5 executed successfully 7 i.
Bow ) The 'og "enerated after /SA$ES_C&%FI' was executed . "i&e the specific one &ariant) which you want to execute in &ariant field of Start Aptions window.
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-D npro= applications .// 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.
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( . This is one of the ma or features of eCATT that allows users to test business processes that cross system boundaries.D npro Application This $eblog will discuss how to create a Test Case for a 0e.A.eCATT Tutorial eCATT Tutorial submitted by Sumeet Kaul.5C 4estination > $E64+B!. This is one of the ma or features of eCATT that allows users to test business processes that cross system boundaries.
eCATT: Creating a Test Case for a 0e. In my pre&ious $elogs on eCATT ) I discussed topics starting from <Introduction to eCATT< to <Executing a Test Case using eCATT <.D n!ro Application. The application will be tested for different set of data . This $eblog will go a step further and discuss how to create a Test Case for a 0eD n!ro Application. Tcode > S9FP . The application is for !urchase Arder Creation. ) Type > " Target Dost > Nser&erO Ser&ice > NportO
.5C destination in SA! . 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 .
Tcode > SECATT
After creation of Test 4ata Container ) Create Test Script .
.5C destination created abo&e .A command . 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!.Bow ) create a System data Container assigning DTT! . Entering System data Container and Target System .
The Application in our case is G0webdynpro0dispatcher0local0!A0Create!A=
. The application starts in the browser .
.ecording starts .
.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 .
A command is created for each page of application.ecording= Aption .
6elow we can see a $E64+B!.
.Bow ) clic( GStop .
Bow !arameteri*e the Input &alues
Creating Test 4ata Container .
Bow Creating Test Configuration and attaching Test 4ata Container . The Company code data is different in both cases . 5or Test Iariant E > Company Code is E///. Iariants for are created . > Company Code is 1///..
. 5or Test Iariant .
7 Company Code >1/// 8
.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.
Thus we were able to successfully Create a Test Case for a 60e.
.D npro Application6 deployed on %a&a Stac( using eCATT.