ECATT Scripts Creation

8/10/2019 ECATT Scripts Creation

1/27

eCATT Scripts Creation TCD Mode (PART II)

The Part I of eCATT Introduction gives the basic details about usage of eCATT & features

involved. In Part II, the creation of eCATT scripts using TCD mode of recording will be explainedin detail. In the subse uent Parts, !AP"#I recording mode of recording and other details ofeCATT will be covered.

Steps Involved In Creation Of eCATT Test Scripts:

Test script is generall$ series of steps %transactions involving a businessscenario. Identification of right transactions for this script, which prepares the input data forthe script and also covers the planned business scenario, should be done.

'ecording of test script b$ selecting proper recording mode. (xecution of test script immediatel$ after recording without parameteri)ation to

confirm the errorless recording. Parameteri)ation of the import, export & variable parameters. Preparing variants using Test Data Container. *in+ing Test !cript %T! & Test Data Container %TD b$ Test Configuration %TC . (xecution of T! using TC for different ariants.

How To Identify Any Transaction For TCD Recording Mode:

If the transaction runs under !AP "#I for -indows or !AP "#I for ava, it can berecorded b$ either TCD or !AP "#I mode.

If the transaction doesn/t have an$ activex controls then TCD recording mode can beused.

If the transaction has activex controls and these controls are 01T mandator$ for thefunctionalit$ of the transaction, then also TCD mode can be used as recording mode.

Key Feat res Of TCD Recording Mode:

It is suitable for the transactions not having activex controls, so it doesn/t re uire an$ "#Ipla$bac+ mode.

It is ver$ fast. It has its own built in screen simulation for standard screen elements. 2ence while

execution, the controls are deactivated and the user/s actions are simulated b$ reading therecorded data flow.

Steps For Recording !sing TCD Mode:

Transaction !(CATT. "ive the name of the Test !cript %T! in Test !cript input box. The ersion input b$

default is with value 3. In the Attributes 45"eneral Data Tab, the value of the Component will be 6C4T-64T!T4

(CA for eCATT. In the test script editor, choose the (ditor tab. Choose Pattern button from the application toolbar. The Insert !tatement dialog box appears. 7rom the Command Dropdown *ist, choose

TCD %'ecord .

1


2/27

In the Transaction field, enter the transaction code of the transaction that $ou want torecord, and choose (nter.

In the Interface field, a s$stem4generated name appears. Accept the s$stem4generated name or edit it. If there is a s$stem data container, $ou can enter the target s$stem in the Target !$stem

field. Choose (nter. The transaction starts recording.

-or+ through the transaction as normal. -hen $ou leave the transaction, the s$stemreturns $ou to the script editor with the 'ecording ended dialog box. Choose 8es to transfer the data. ATCD command and its associated Command Interface will be inserted in test script

editor of !(CATT

"#ec tion of Recorded TCD script:

1nce the recording of the transaction is done and the details of recording are ta+enbac+ to the test script editor, script can be executed.

2


3/27

7irst of all without parameteri)ation the script should be executed to confirm the errorlessrecording. At the runtime, a !tart 1ptions window appears. "ive the following values onthis window 9 (rror 6ehavior with value ! 0o termination, continue with next script.

!$stem Data 9 0ame of the s$stem data container, which contains the Target !$stem. Target !$stem 9 0ame of the server on which the execution will happen. !elect the *og Displa$ chec+ box. In TCD section of window, select 0 9 Process in bac+ground, s$nchronous local. Clic+ on (xecute button.

Transaction will start executing, which appears at the bottom. If the recording is error free, then success log will appear. And if there is an$ error in

recording of the transaction and its repla$ then error log with details will appear. After the confirmation of error free recording, one can go ahead with parameteri)ation of

the import, export & variables. In !(CATT transaction using Test Data %TD , variants can be prepared for the recorded

test script. In the Parameters tab, add all the parameters from the test script. This will appearas (CATTD(7A#*T in the ariants tab. Add multiple variants, as per re uirement in theariants tab. Test Data is independent of test script. 2ence can be reused wherever re uired.

In !(CATT transaction using Test Configuration %TC , the TD & T! can be lin+ed together

on the Configuration tab. 1n the ariants tab, using ariant :aintenance Assistant re uiredvariants values from TD could be lin+ed to TC.

7inall$ the TC can be executed from !(CATT directl$ b$ giving the re uired variant nameat runtime.

The TC is used in managing the scripts in plans;pac+ages using !CAT transaction.

3


4/27


5/27

$%at is re( ired if t%e C%ec&points s%o ld )e added as a part of TestA to'ation:

Chec'points should be added as a part of manual script at the design time.

2here the chec'points ill be veri$ed for the given scenario should be clearl% mentioned in themanual script. e.g. hether table value ill be veri$ed or an% value in the transaction ill be

veri$ed.

At hat stage in the complete test scenario, chec'points should be veri$ed should also bementioned ver% clearl% in manual test script.

The value of the chec'points for the given scenario should be clearl% given as input in the manualtest script.

$%at are co''ands in eCATT for C%ec&points: There are di3erent eCATT commands are available, hich can be used for veri$cation of

chec'points as follo s 4 CHEGUI, CHETAB, CHEVAR, CHEATTR, CHESTATIC etc.

Details a)o t c%ec&point co''ands in eCATT:

:ost fre uentl$ used commands for chec+points are C2("#I, C2(TA6, and C2( A'.

CH"*AR co''and:

C05"A+ command compares one parameter ith other parameter or $xed value. S%ntax6 CHEVAR ( ) . 7or comparison,

the operators are , , , < ! > . 7or complex expressions, the operators li'e A"#, $R % "$T are available.

C05"A+ command is useful hen t o values need to be compared. /ne value ill be as aninput for veri$cation and the other one ma% be either input vale or $xed value or outcome from theexecution of the business scenario as 5xport variable. Also this is useful hen depending on some

output value8 the further steps need to be veri$ed for execution. If this command fails at runtime, then error log is generated.

5xample6

o oto transaction SECATT .o ive the name for a Test Script. Clic' on Create .

o ive the suitable Tit&e & Component in the Attri' tes tab.o +ecord a transaction.

o Parameteri#e the $elds of the transaction.o Position the cursor in the eCATT editor after the transaction recording.

o )o clic' on attern (Insert Statement Ctr&*+ ) button from the application toolbar.

5


6/27

Select arams from the Gro p dropdo n, CHEVAR from the Comman- dropdo n. In the Condition,enter .IV."A/E.+IRST .CV.+"A/E and clic' on 5nter.

o The C05"A+ command is inserted in to the command editor of eCATT.

)o , give the suitable values to input as ell as chec'point variable in the arameter section.

5xecute the script. The log ill be generated. 0ere the input value is di3erent than the chec'point value so the

CHEVAR command should fail & hence the script.

6


7/27

And if the correct value is passed to the chec'point, success log is generated as follo s *

CH"+!I co''and:

C05 !I command is useful hen the $eld value to be veri$ed is present in an% transaction. There are t o a%s of using the C05 !I command, one is d%namicall% adding this

command during record time in SAP !I recording mode & other is manuall% in eCATT 5ditor. The$rst approach is ver% simple and should be follo ed for errorless recording.

If the transaction is not part of the business scenario then record this transaction in SA GUIrecording mode after the normal business scenario is recorded in the same script. And if in case thetransaction, hich contains the chec'point to be veri$ed is part of the given business scenario then

ma'e sure that at least transaction is getting recorded in SA GUI mode. If this command fails at run time then error log is generated.

5-A9P(56

oto transaction SECATT .

7


8/27

ive the name for a Test Script. Clic' on Create . ive the suitable Tit&e & Component in the Attri' tes tab.

+ecord a transaction in SA GUI mode. 7or this clic' on attern (Insert Statement Ctr&*+ )button from the application toolbar.

Select A&& Comman-s from Gro p dropdo n & SA GUI Rec from Command dropdo n. Clic' on 5nter.

o )o from the Recor- SA GUI Comman- popup, select the chec'boxes for A tomatic Generation & give the transaction name to be recorded. Clic' on Start Recor-in0 button.

o /n the Recor- SA GUI Comman- popup, clic' on es to record the session.o /n the Recor- R nnin0 popup, clic' on 5nter. This is the screen having Insert

C05 !I Command into, hich e ill utili#e for chec'point.

8


9/27

o )o start recording of the transaction on the session ust behind the above popup.+ecord the transaction as per re uirement. )o here hile recording, herever the chec'point $eld

comes on the screen, ust bring the popup of Recor-in0 R nnin0 on this chec'point screen. Thispopup remains till e stop the recording.

o )o clic' on Insert CHEGUI Comman- from this popup & point to ards the re uired$eld on the transaction.

o The moment mouse is moved over on the screen, the area is highlighted. So go tothe re uired $eld and clic' there once.

9


10/27

o The moment the chec'point $eld is clic'ed, hich got highlighted, another popupcomes up Se&ection o3 roperties % /et4o-s to Be Recor-e- . 5xpand the node C4ec5s . And select all

the chec'boxes. Clic' on Insert % E6it at the bottom.

o After this, ust go to the recording of transaction and al' through the transactionas re uired. Come bac' till SAP 5as% Access screen.

o /nce the recording is done, clic' on the Stop Recor-in0!!! from the Recor-in0R nnin0!!! popup. This ill get bac' the recorded script in Solution 9anager.

10


11/27

The Part I of eCATT Introduction gives the basic details about usage of eCATT & features involved. InPart II, the creation of eCATT scripts using TCD mode of recording is explained in detail. In the Part III,

the creation of eCATT Scripts using SAP !I mode is explained in detail. In Part I" chaining,parameteri#ation, creation of Test Con$guration, Test Data Container, and S%stem Data Container

are explained in detail. In Part ", the management of eCATT Scripts via Test or'bench is explained.In Part "I, the eCATT (ogs is explained in detail. In Part "II, creation of eCATT Scripts using )on*!ser

Interface mode is explained along ith the details of Cop%, +ename, Delete, !pload and Do nload of eCATT ob ects. In the Part "III, tips & lin's of eCATT are covered.

In part I-, the chec'points using eCATT ill be covered.

$%at are C%ec&points in Testing:

Chec'points are the values to be veri$ed hich con$rms the successful testing. These Chec'pointsill have al a%s prede$ned values as per the business re uirements and should match to the output

results after testing. So Chec'points are used for cross veri$cation of the results of testing.

$%y are C%ec&points needed in A to'ated Testing:

In case of manual testing, once the testing is done b% the business anal%st for the given scenario,the anal%st ill manuall% cross verif% the value of the chec'point either in the table or in some

transaction.

This value might be coming from SP+/ settings, hich is placed in those tables or transactions as aresult of execution of the testing scenario.

/nce the chec'point value is veri$ed then onl% the testing is con$rmed as successful. This processof veri$cation is $ne in case of manual testing but in case of automated testing, the chec'points

need to be part of automation.

If the chec'point is not part of automated testing then the chances of having successful automatedtest result ith incorrect chec'point value increases & hence resulting in incorrect testing. As here

the chec'point needs to verif% manuall% for the automated result set.

0ence the need of adding chec'points in the automated testing is must to con$rm the successfultesting.

Advantages of C%ec&points in A to'ation:

If the chec'point ill be as part of automation of test case then the manual error of cross veri$cationis avoided.

If the test scenario is automated but chec'point is manual then the chances of missing the crossveri$cation for the chec'point is more. This happens mostl% hen the integration test happens and

go live is about to happen ith cut over activities on the head of business anal%st. As lots of activities are needed to be done in less time, the chec'point cross veri$cation ma% be missed out.

It ill be done automaticall%. 0ence time e1cient.

$%at is re( ired if t%e C%ec&points s%o ld )e added as a part of TestA to'ation:

Chec'points should be added as a part of manual script at the design time.

11


12/27

2here the chec'points ill be veri$ed for the given scenario should be clearl% mentioned in themanual script. e.g. hether table value ill be veri$ed or an% value in the transaction ill be

veri$ed.

At hat stage in the complete test scenario, chec'points should be veri$ed should also bementioned ver% clearl% in manual test script.

The value of the chec'points for the given scenario should be clearl% given as input in the manualtest script.

$%at are co''ands in eCATT for C%ec&points:

There are di3erent eCATT commands are available, hich can be used for veri$cation of chec'points as follo s 4 CHEGUI, CHETAB, CHEVAR, CHEATTR, CHESTATIC etc.

Details a)o t c%ec&point co''ands in eCATT:

:ost fre uentl$ used commands for chec+points are C2("#I, C2(TA6, and C2( A'.

CH"*AR co''and:

C05"A+ command compares one parameter ith other parameter or $xed value. S%ntax6 CHEVAR ( ) . 7or comparison,

the operators are , , , < ! > . 7or complex expressions, the operators li'e A"#, $R % "$T are available.

C05"A+ command is useful hen t o values need to be compared. /ne value ill be as aninput for veri$cation and the other one ma% be either input vale or $xed value or outcome from theexecution of the business scenario as 5xport variable. Also this is useful hen depending on some

output value8 the further steps need to be veri$ed for execution. If this command fails at runtime, then error log is generated.

5xample6

o oto transaction SECATT .o ive the name for a Test Script. Clic' on Create .

o ive the suitable Tit&e & Component in the Attri' tes tab.o +ecord a transaction.

o Parameteri#e the $elds of the transaction.o Position the cursor in the eCATT editor after the transaction recording.


Select arams from the Gro p dropdo n, CHEVAR from the Comman- dropdo n. In the Condition,enter .IV."A/E.+IRST .CV.+"A/E and clic' on 5nter.

12


13/27

o The C05"A+ command is inserted in to the command editor of eCATT.

)o , give the suitable values to input as ell as chec'point variable in the arameter section.

5xecute the script. The log ill be generated. 0ere the input value is di3erent than the chec'point value so the

CHEVAR command should fail & hence the script.

13


14/27

And if the correct value is passed to the chec'point, success log is generated as follo s *

CH"+!I co''and:

C05 !I command is useful hen the $eld value to be veri$ed is present in an% transaction. There are t o a%s of using the C05 !I command, one is d%namicall% adding this

command during record time in SAP !I recording mode & other is manuall% in eCATT 5ditor. The$rst approach is ver% simple and should be follo ed for errorless recording.

If the transaction is not part of the business scenario then record this transaction in SA GUI

recording mode after the normal business scenario is recorded in the same script. And if in case thetransaction, hich contains the chec'point to be veri$ed is part of the given business scenario then

ma'e sure that at least transaction is getting recorded in SA GUI mode. If this command fails at run time then error log is generated.

5-A9P(56

oto transaction SECATT . ive the name for a Test Script. Clic' on Create .

ive the suitable Tit&e & Component in the Attri' tes tab.

14


15/27

+ecord a transaction in SA GUI mode. 7or this clic' on attern (Insert Statement Ctr&*+ )button from the application toolbar.

Select A&& Comman-s from Gro p dropdo n & SA GUI Rec from Command dropdo n. Clic' on 5nter.

o )o from the Recor- SA GUI Comman- popup, select the chec'boxes for A tomatic Generation & give the transaction name to be recorded. Clic' on Start Recor-in0 button.

o /n the Recor- SA GUI Comman- popup, clic' on es to record the session.o /n the Recor- R nnin0 popup, clic' on 5nter. This is the screen having Insert

C05 !I Command into, hich e ill utili#e for chec'point.

o )o start recording of the transaction on the session ust behind the above popup.+ecord the transaction as per re uirement. )o here hile recording, herever the chec'point $eld

15


16/27

comes on the screen, ust bring the popup of Recor-in0 R nnin0 on this chec'point screen. Thispopup remains till e stop the recording.

o )o clic' on Insert CHEGUI Comman- from this popup & point to ards the re uired$eld on the transaction.

o The moment mouse is moved over on the screen, the area is highlighted. So go tothe re uired $eld and clic' there once.

16


17/27

o The moment the chec'point $eld is clic'ed, hich got highlighted, another popupcomes up Se&ection o3 roperties % /et4o-s to Be Recor-e- . 5xpand the node C4ec5s . And select all

the chec'boxes. Clic' on Insert % E6it at the bottom.

o After this, ust go to the recording of transaction and al' through the transactionas re uired. Come bac' till SAP 5as% Access screen.

o /nce the recording is done, clic' on the Stop Recor-in0!!! from the Recor-in0R nnin0!!! popup. This ill get bac' the recorded script in Solution 9anager.

17


18/27

o )o parameteri#e the $elds of the transaction along ith the chec'point. 7orchec'point parameteri#ation, double clic' on the interface name on the left side in the command

editor. /n the right side, expand the Text node. In the E6pecte- Res &t , on the rightmost side, enterthe name of the parameter. This is the parameter to hich input values ill be passed for

veri$cation of chec'point.

o )o give some input value to chec'point parameter in the arameter section andexecute.

o The log ill be generated. 0ere as the input value is di3erent than the valuepresent in s%stem for chec'point, the error log ill be generated.

18


19/27


20/27

Database updates after transactions or 2hether a particular table entr% exists or Customi#ing tableentries.

There is no restriction in giving 'e% $elds. At least ? should be entered in 'e% $elds. It is bestif all the values are present for complete 'e% of table.

If there is no record in database table for the given chec'point, then error log is generated.And if an% record exists then success log is generated.

The values hich are passed to C05TA: command should be in the format, hat s%stemunderstands internall%. This is e uivalent to passing values to S5(5CT uer% considering all input

conversions. 5.g. date internall% is interpreted onl% in @@@@99DD format. 5xample6

o oto transaction SECATT . ive the name for a Test Script. Clic' on Create.o ive the suitable Tit&e & Component in the Attri' tes tab.

o +ecord a transaction. Parameteri#e the $elds of the transaction.o Position the cursor in the eCATT editor after the transaction recording.


o Select A&& Comman-s from Gro p dropdo n & CHETAB from the Comman-dropdo n. ive the name of the table in Table and clic' on 5nter. It ill insert the command in the

eCATT editor. Double clic' on the interface name from this command from the left side8 on right sideit ill open a structure as that of table.

o )o parameteri#e the chec'point. 7or this, clic' on the command interface of C05TA: command. /n the right most side, in the "alue of the re uired $eld, enter the input

parameter name. Also pass the values for the 'e% $elds of the table.

20


21/27

o Pass some value to chec'point & execute the script. As here the value hich ill beupdated in the database is di3erent than the chec'point input value, the script ill fail ith error log.

o And if correct value is passed for the chec'point, the script ill generate successlog.

CH"ATTR co''and:

C05ATT+ is used to compare the value of the global class public instance attribute.

S%ntax6 CHEATTR (

21


22/27

eCATT Tips Of Recording, Testing !inks (PART "III)

The Part I of eCATT Introduction gives the basic details about usage of eCATT & features involved. In Part II, thecreation of eCATT scripts using TCD mode of recording is explained in detail. In the Part III, the creation of eCATT

!cripts using !AP"#I mode is explained in detail. In Part I chaining, parameteri)ation, creation of TestConfiguration, Test Data Container, and !$stem Data Container are explained in detail. In Part , the management

of eCATT !cripts via Testwor+bench is explained. In Part I, the eCATT *ogs is explained in detail. In Part II,creation of eCATT !cripts using 0on4#ser Interface mode is explained along with the details of Cop$, 'ename,

Delete, #pload and Download of eCATT ob


23/27

o Transaction with dropdown without +e$s setting 9

Transaction with dropdown +e$s settings 9

If the recording includes, adding some value to the table then don/t scroll up to blan+ line.#se directl$ the Create Item icon and then add the new values. !crolling fails at the time of

23


24/27

repla$.

If the recording includes searching some value from A* grid and the value is +nown thendon/t scroll and loo+ for the value. #se the !earch icon from the A* toolbar for searching. 1nce

the search item is found, then clic+ on the item for further processing.

It happens at times that the screen si)e reduces at the time of recording in width andheight. In such scenario if the field to be captured during recording is present somewhere at the

bottom, then don/t scroll. #se the TA6 +e$ till that field is reached. Due to !croll functionalit$possibilit$ of script failure becomes high.

It is not possible to capture the value from a d$namicall$ generated list. If the recordingincludes a d$namicall$ generated list and one value %which is not +nown until execution from thislist needs to pass to the subse uent step in recording then use foreground mode of recording for

this d$namicall$ generated list. #se -AIT @@@ statement after its recording. During this -AIT@@@ seconds, capture the value from the generated list manuall$ and pass it to the next

recording.

SAP *I TCD Recording Modes

(rror messages can be recorded and repla$ed b$ 1nl$ !AP"#I recording mode and01T b$ TCD mode.

-arning messages are automaticall$ handled b$ TCD mode but in !AP"#I recordingmode the$ need to be handled if the$ re uire user intervention for further processing. %(.g.

Pressing and enter +e$ will enable all the fields after warning message !creens can be made 1ptional for execution in !AP"#I mode. This optional screen will

be handled automaticall$ at runtime even if not in the screens flow. 6ut in TCD screens can/t bemade optional which ma$ or ma$ not occur during execution. 'ather in TCD screens can be

24


25/27

made active or deactivated in the cases where depending on some input values, the recordingcan be reused. The screens se uence should be +nown well in advance in TCD for ma+ing an$

screen active or not. 1nl$ local variables from the eCATT Parameters can be used in Inline A6AP code. Import

and (xport parameter are not allowed. Passing values to subse uent screens at runtime is onl$ possible in !AP"#I and not in

TCD mode. !AP"#I Confirm Popup

In order to avoid the following popup for !AP"#I recording, option is available in ';= !$stem +

Clic+ on the icon with tool tip Customi)ing 1f *ocal *a$out %Alt?73> in the standard toolbar onan$ transaction of ';= s$stem. !elect the 1ptions menu.

7rom the 1ptions 45 !cripting, unchec+ the chec+ box of 0otif$ when a script attaches to arunning "#I. Clic+ on Appl$ 45 1+. The popup won/t appear onwards.

Making SAPGUI Screen Optional

It is possible in !AP"#I recording mode to ma+e screens optional.Double clic+ on the screen or message popup, which needed to ma+e optional on the left side in

the command editor. 1n right side, the interface will open. #nder the Processed!creen node, firstoption is Active B@B.

Change Active B@B to B1B.

25


26/27

B@B 4 Active %Compulsor$ will executeB1B 4 1ptional %will execute onl$ when it will be in execution flow .

eCATT Commands:

An eCATT script consists of individual eCATT commands. (ach command begins with acommand word and ends with a period. Comments % and assignments % are exceptions to this

rule.

There can be several commands on the same line. Comments % , assignments % , andinline A6AP are exceptions to this rule.

(.g. of eCATT Commands are 4, , A6AP, C2(TA6, C2( A', C*(A', D1, (*!(, (*!(I7, (0DA6AP, (0DD1, (0DI7,

(0D:(!!A"(, (@IT, 7#0, "(TTA6, I7, *1", :(!!A"(, 10E*A!TE:(!!A"(EC2(CF,'(7, '(7CATT, '(7(@T, '(:1T(CATT, '(!TA6, !AP"#I, !(0D(@T, !(TTA6, TCD, -AIT,

-AITE10ED80P'1 There are examples involving these eCATT commands, which can be found from the

menu "oto45 #se 1f Command.1n the next screen eCATT 9 !earch 1f eCATT Commands in Test !cript, in the Command input

field, give the name of the eCATT Command from the 7G help.

And clic+ on (xecute %7H button from the application toolbar. *ist of examples will be inthe output.

26


27/27

Key -oints Can ,e Followed For S ccessf l Testing *ia eCATT :

Anal%sis of transactions ith di3erent behaviors for di3erent sets of data.7inall% selecting the set of data, hich gives maximum possible messages popup for

the given transaction. Automation along ith the veri$cation before $nal regression on Bualit%

Server. Preparation of variant $les ith details having comments on each value, hich

helps in preparation of data for the scripts before execution. Anal%#ing the behavior of transactions for the bac'ground foregroundexecution mode. Accordingl% preparation of pac'ages for bac'ground & foregroundexecution. Preparing the prere uisites for the regression as a hole considering the

user ID settings. Also the transaction settings for those user IDs .

9aintaining the results in scorecard ith log IDs for each location the scriptsbeing tested during regression on Bualit%. This helps for future reference of script

results. Scorecard can be something li'e as follo s *

Sapna Modi

Documents

ECATT Scripts Creation