Checkpoints in eCATT (Part IX)
: / 168
 
Administrator   
24.01.2009 .
 

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 is explained in detail. In the Part III, the creation of eCATT Scripts using SAPGUI mode is explained in detail. In Part IV chaining, parameterization, creation of Test Configuration, Test Data Container, and System Data Container are explained in detail. In Part V, the management of eCATT Scripts via Testworkbench is explained. In Part VI, the eCATT Logs is explained in detail. In Part VII, creation of eCATT Scripts using Non-User Interface mode is explained along with the details of Copy, Rename, Delete, Upload and Download of eCATT objects. In the Part VIII, tips & links of eCATT are covered.
In part IX, the checkpoints using eCATT will be covered.

What are Checkpoints in Testing:

Checkpoints are the values to be verified which confirms the successful testing. These Checkpoints will have always predefined values as per the business requirements and should match to the output results after testing. So Checkpoints are used for cross verification of the results of testing.

Why are Checkpoints needed in Automated Testing:

 In case of manual testing, once the testing is done by the business analyst for the given scenario, the analyst will manually cross verify the value of the checkpoint either in the table or in some transaction.

 This value might be coming from SPRO settings, which is placed in those tables or transactions as a result of execution of the testing scenario.

 Once the checkpoint value is verified then only the testing is confirmed as successful. This process of verification is fine in case of manual testing but in case of automated testing, the checkpoints need to be part of automation.

 If the checkpoint is not part of automated testing then the chances of having successful automated test result with incorrect checkpoint value increases & hence resulting in incorrect testing. As here the checkpoint needs to verify manually for the automated result set.

 Hence the need of adding checkpoints in the automated testing is must to confirm the successful testing.

Advantages of Checkpoints in Automation:

If the checkpoint will be as part of automation of test case then the manual error of cross verification is avoided.

If the test scenario is automated but checkpoint is manual then the chances of missing the cross verification for the checkpoint is more. This happens mostly when the integration test happens and go live is about to happen with cut over activities on the head of business analyst. As lots of activities are needed to be done in less time, the checkpoint cross verification may be missed out.

It will be done automatically. Hence time efficient.

 
What is required if the Checkpoints should be added as a part of Test Automation:

 Checkpoints should be added as a part of manual script at the design time.

 Where the checkpoints will be verified for the given scenario should be clearly mentioned in the manual script. e.g. whether table value will be verified or any value in the transaction will be verified.

 At what stage in the complete test scenario, checkpoints should be verified should also be mentioned very clearly in manual test script. 

 The value of the checkpoints for the given scenario should be clearly given as input in the manual test script.

 
What are commands in eCATT for Checkpoints: 

 There are different eCATT commands are available, which can be used for verification of checkpoints as follows CHEGUI, CHETAB, CHEVAR, CHEATTR, CHESTATIC etc.

Details about checkpoint commands in eCATT:

Most frequently used commands for checkpoints are CHEGUI, CHETAB, and CHEVAR. 

 CHEVAR command: 

  • CHEVAR command compares one parameter with other parameter or fixed value. 
  •  Syntax: CHEVAR (<parameter1> <comparison operator> <parameter2>). For comparison, the operators are =, <>, <, >, <=. >=. For complex expressions, the operators like AND, OR & NOT are available. 
  •  CHEVAR command is useful when two values need to be compared. One value will be as an input for verification and the other one may be either input vale or fixed value or outcome from the execution of the business scenario as Export variable. Also this is useful when depending on some output value; the further steps need to be verified for execution. 
  •  If this command fails at runtime, then error log is generated. 
  •  Example: 

    • Goto transaction SECATT
    • Give the name for a Test Script. Click on Create
    • Give the suitable Title & Component in the Attributes tab. 
    • Record a transaction. 
    • Parameterize the fields of the transaction. 
    • Position the cursor in the eCATT editor after the transaction recording. 
    • Now click on Pattern (Insert Statement Ctrl+F6) button from the application toolbar.



Select Params from the Group dropdown, CHEVAR from the Command dropdown. In the Condition, enter P_IV_NAME_FIRST = P_CV_FNAME and click on Enter.


    • The CHEVAR command is inserted in to the command editor of eCATT.
 
  • Now, give the suitable values to input as well as checkpoint variable in the Parameter section.
  • Execute the script.
  • The log will be generated. Here the input value is different than the checkpoint value so the CHEVAR command should fail & hence the script.



  • And if the correct value is passed to the checkpoint, success log is generated as follows -

CHEGUI command:

  • CHEGUI command is useful when the field value to be verified is present in any transaction.
  • There are two ways of using the CHEGUI command, one is dynamically adding this command during record time in SAPGUI recording mode & other is manually in eCATT Editor. The first approach is very simple and should be followed for errorless recording. 
  • If the transaction is not part of the business scenario then record this transaction in SAPGUI recording mode after the normal business scenario is recorded in the same script. And if in case the transaction, which contains the checkpoint to be verified is part of the given business scenario then make sure that at least transaction is getting recorded in SAPGUI mode.
  • If this command fails at run time then error log is generated.
  • EXAMPLE:
  • Goto transaction SECATT.
  • Give the name for a Test Script. Click on Create
  • Give the suitable Title & Component in the Attributes tab. 
  • Record a transaction in SAPGUI mode. For this click on Pattern (Insert Statement Ctrl+F6) button from the application toolbar.

Select All Commands from Group dropdown & SAPGUI Rec from Command dropdown. Click on Enter. 

    • Now from the Record SAP GUI Command popup, select the checkboxes for Automatic Generation & give the transaction name to be recorded. Click on Start Recording button.


    • On the Record SAP GUI Command popup, click on Yes to record the session. 
    • On the Record Runningpopup, click on Enter. This is the screen having Insert CHEGUI Command into, which we will utilize for checkpoint.


    • Now start recording of the transaction on the session just behind the above popup. Record the transaction as per requirement. Now here while recording, wherever the checkpoint field comes on the screen, just bring the popup of Recording Running on this checkpoint screen. This popup remains till we stop the recording.


    • Now click on Insert CHEGUI Command from this popup & point towards the required field on the transaction.


    • The moment mouse is moved over on the screen, the area is highlighted. So go to the required field and click there once.


    • The moment the checkpoint field is clicked, which got highlighted, another popup comes up Selection of Properties & Methods to Be Recorded. Expand the node Checks. And select all the checkboxes. Click on Insert & Exit at the bottom.


    • After this, just go to the recording of transaction and walk through the transaction as required. Come back till SAP Easy Access screen. 
    • Once the recording is done, click on the Stop Recording... from the Recording Running... popup. This will get back the recorded script in Solution Manager.


    • Now parameterize the fields of the transaction along with the checkpoint. For checkpoint parameterization, double click on the interface name on the left side in the command editor. On the right side, expand the Text node. In the Expected Result, on the rightmost side, enter the name of the parameter. This is the parameter to which input values will be passed for verification of checkpoint.

 

    • Now give some input value to checkpoint parameter in the Parameter section and execute. 
    • The log will be generated. Here as the input value is different than the value present in system for checkpoint, the error log will be generated.


    • And if the correct value is passed as an input to checkpoint, than success log is generated as follows -


CHETAB command: 

  • CHETAB command is useful for verifying the values in the database tables. This value will be updated after the business scenario is executed. Also this value will be directly coming from SPRO settings into the database table. 
  • Syntax: CHETAB (<tablename>,<command interface>). Here the structure of the Command Interface is same as the structure of table. One can verify following from CHETAB command in eCATT
    Database updates after transactions or Whether a particular table entry exists or Customizing table entries. 
  • There is no restriction in giving key fields. At least * should be entered in key fields. It is best if all the values are present for complete key of table. 
  • If there is no record in database table for the given checkpoint, then error log is generated. And if any record exists then success log is generated. 
  • The values which are passed to CHETAB command should be in the format, what system understands internally. This is equivalent to passing values to SELECT query considering all input conversions. E.g. date internally is interpreted only in YYYYMMDD format. 
  • Example: 
    • Goto transaction SECATTGive the name for a Test Script. Click on Create.
    • Give the suitable Title & Component in the Attributes tab. 
    • Record a transaction. Parameterize the fields of the transaction.
    • Position the cursor in the eCATT editor after the transaction recording. 
    • Now click on Pattern (Insert Statement Ctrl+F6) button from the application toolbar.


    • Select All Commands from Group dropdown & CHETAB from the Command dropdown. Give the name of the table in Table and click on Enter. It will insert the command in the eCATT editor. Double click on the interface name from this command from the left side; on right side it will open a structure as that of table.


    • Now parameterize the checkpoint. For this, click on the command interface of CHETAB command. On the right most side, in the Value of the required field, enter the input parameter name. Also pass the values for the key fields of the table.


    • Pass some value to checkpoint & execute the script. As here the value which will be updated in the database is different than the checkpoint input value, the script will fail with error log.


    • And if correct value is passed for the checkpoint, the script will generate success log. 

 CHEATTR command: 

  • CHEATTR is used to compare the value of the global class public instance attribute. 
  • Syntax: CHEATTR (
Sapna Modi is a Software Engineer.
 

: 19952

(21)
 
xylihkn
IP: 91.232.96.4
 
iofcup, 04:04 25 2012 .
 
dxhluou http://ipcdqd.com/ skhtqf [url=http://axsvjm.com/]skhtqf[/url]
IP: 91.232.96.4
 
viagra, 07:20 25 2012 .
 
This intimidation pocliy is gradually expanding.In New York City there are police units running around in combat gear with assault rifles, which my husband (a retired NSW guy) and one of our closest friends, an upper tier security guy, both scoff at: The terrorists they are supposed to be protecting us from do not look to get into a gunfight, they are here to blow things up.In various large subway and train stations here, the police will suddenly appear with a table and randomly search backpacks, etc.The guys' opinion of that is that it's simply another placebo, more programming to accustom We, The People to more of the same: If a bomber's already in the station where the table is located, the authorities have failed in their job (he's already in a potential kill zone ), because as soon as they order the terrorist to submit to a bag search, the last thing they'll ever hear will be Alahu Akbar! and then the subject will self detonate , as the guys put it, killing everybody within the bomb's overpressure range. Then the police involved will be hailed as heroes rather than political sacrificial lambs.The TSA is about as relevent as these police where protecting the public is concerned, all show, while their intimidating demand for compliance programs us to the kind of thing I saw in Cuba as a child and people in other third world dictatorships see all the time as well: Cops/soldiers walking the streets with machine guns and the authority to inconvenience or bully anyone they choose.We'll no doubt be seeing this increase, incrementally, in the future.Mrs Wolf recently posted..
IP: 131.188.11.53
 
Edward, 16:15 17 2012 .
 
Jeffrey, The bride and I traveled to New York via plane and then three days later beodrad the Queen Mary 2. With all our baggage in hand, the screening at ship board was smoother, faster and more appropriate than the airport screening. Now, when you consider that there are over 2000 passengers to protect, you'd think this would be cause for very, very very careful screening yet, it may have been, but was FAR LESS intrusive than the damn TSA checks at our local airport and the La Guardia when we returned home after our cruise. TSA Touching Stuff Awfully
IP: 193.23.123.61
 
Ghanshyam, 20:35 17 2012 .
 
t4hvzD zgknqjgcomsf
IP: 95.138.142.30
 
iposnueo, 13:47 18 2012 .
 
Bo83Bu , [url=http://aidzmxdnbyzg.com/]aidzmxdnbyzg[/url], [link=http://immdsieekdrr.com/]immdsieekdrr[/link], http://axiymifcmyge.com/
IP: 223.165.31.61
 
bsfuyuvq, 01:01 19 2012 .
 
cLzGPG dmvizknjgwgj
IP: 199.116.173.44
 
nxnunk, 10:14 19 2012 .
 
bDSUJW , [url=http://ziqteoymgegl.com/]ziqteoymgegl[/url], [link=http://gnzbniiyxlkr.com/]gnzbniiyxlkr[/link], http://qjwputhcwbtz.com/
IP: 62.234.124.37
 
qfrngafl, 10:42 21 2012 .
 
Hi thanks for the ttourial! But after my exactly following your steps I met a really strange problem: I put 3 player starts in my level, after I triggered them all, I kept dying to test it and found that my charactor just respawn from thses 3 player starts in sequence! Which like first death->player start 3; second death->player start 2; third death->player start 1; fourth death->player start 3 again So could you give me any suggestions about this? Thanks in advance!Well-loved.
IP: 86.114.160.253
 
Emirhan, 11:32 21 2012 .
 
it wasn’t good, so He made a woman FOR HIM, that was the point of our creation. Of cousre everything changes, evolves, & matures, but the core of our existence is still the same. But what if we were raised outside of America, how would we view our womanhood, men, family, and marriage?My views on marriage (and a lot of other things) are different than most in America, but I’m glad for that. Marriage is necessary, it’s the right way of how we “bear fruit and increase upon the Earth.” And to me that’s more than just having kids, that means bringing up people with morals and values so the world will be subdued by them and not the other way around. One of the problems we’re missing on both sides is righteousness. And I don’t mean the “be Holy, Holy” type of righteousness. I mean the truly treating people with respect, taking responsibility for your actions, blessing your father and mother… type of righteousness. This isn’t Christianity based (as I’m not Christian); I have a Muslim friend who feels the exact way I do and we’re of different beliefs, but I digress… If a man can stand and be honorable, his household will honor him and his children will walk in his footsteps. If a woman can be virtuous and not contentious, then her household will be blessed and her husband and children will esteem her all her days. Me personally, my guideline for how I’m supposed to be is The Torah, I did the best I could w/o it and our marriage was suffering. With Torah, its not perfect, but my gosh its improved tremendously! Also, Its quite easy to point at another’s faults, (even though we are supposed to love correction, it does make us better people) but difficult to face our own. You can’t force others to do/change ANYTHING and we end up frustrated behind it. But if you change yourself into the person you want to be or the person you know you SHOULD be, people around you start to change too. That has been tried and tested with my hubby and even though I recognize it, I’m still working on keeping it action.As for your friends, I’m happy for them and their relationships (in my way of life they’re considered married anyway, lol). I think people add unnecessary pressure to marriage and it fails for various reasons, but not because of the vows. So those are my thoughts, not quite short, but simple enough I hope, lol…
IP: 94.23.238.222
 
Thiago, 04:30 19 2013 .


( 27.02.2009 . )
 
« .
© 2018 ProSapSecurity
Joomla! - , GNU/GPL.