ECATT: Parameterise the ID of a guielement

I want to parameterise the ID of a guielement. At the last position of the ID is defined which element will be use. But it doesen't work. I think, the problem is the length of string, it contains more than 160 characters.
ID = 'wnd[0]/usr/subSUBST:/VWK/ZFW_PROCESS:0100/subACT:
/VWK/VMV_PAV:2200/subSUBSCR_PAV2100:/VWK/VMV_PAV:
2100/tbl/VWK/VMV_PAVTC_PAV_2100/ctxt/VWK/
VMVS_PAV_2100_DY-PARTNER[1,1]'
I work with WEB AS 6.20.
What can I do?
Thanks
Horst

Hello Horst,
in general you can parameterize the whole ID in a SAPGUI command interface.
Unfortunatelly ecatt parameter value length is restricted to 128 char in 6.20. eCATT 6.40 dropped this limitation.
So your 160char ID can not sucessfully replaced by eCATT parameter in 6.20.
But you can parameterize of the ID by the use of a special escape sequence.
Given a parameter PARAM and an ID wnd[0]/abc/Textfield1 you can parameterize the middle part of the ID by setting the parameter PARAM to abc and replacing the ID with wnd[0]/<!PARAM!>/Textfield1.
Hope this helps you out.
Best regards
Jens

Similar Messages

Error when using the REF eCATT command ....

Hi,
When the REF command is used in an eCATT test script to execute another eCATT, only the first REF command executes successfully - all subsequent REF commands fail with these error msgs 'Error in eCATT function SAPGUI', 'Error in Control', 'Message raised at CL_APL_ECATT_LINE_INTERPRETER =CM00K LINE   347'.
Executed separately, the referenced eCATT test scripts are successful.   Executed from one eCATT test script via the REF command, only the first REF command is successful. We are on SAP 6.7 6.40, GUI is 6.40 as well.
Any suggestions would be appreciated - Thanks !

Thanks for the reply, Jonathan.   Still having the same problem after implementing your suggestion.   Any other suggestions you have would be appreciated.
The ResetGUI = 'X' was done for each command interface in the REFerenced test scripts.   The ResetGUI statement was only found immediately after the 'Command Interface' statement (wasn't found after the 'Processed Screen' statement).
The error still happens for the second and all subsequent test scripts referenced by the 'REF' command.   In the failed REF test scripts, the ConnectionID, SessionID, and SystemInfo statements are the failed statments (red lights beside them).   These three statements are immediately after the ResetGUI = 'X' statment (which has a green light).
Different execution options have been tried, including closing, and not closing, generated GUI sessions.
Really at a loss here to figure out how to get the REF statement to work !

Organizing cross-component eCATT tests in the Test Catalog

My question is regarding how to properly structure the test catalog. I have an eCATT test that uses REF to call three other eCATT tests. These three tests are simulating a businses process (order to cash) and they are Creating a Sales Order (VA01), Creating a Delivery (VL01N) and Creating the Billing Document (VF01). Since test catalogs are placed in the application hierarchy I created three separate test catalogs, one for each test. The catalog with VA01 is in component SD-SLS-SO while the catalog with VL01N is in LE-SHP and VF01 is in SD-BIL. Now I have the fourth eCATT script -- the chain script that uses REF to call those other three scripts. Since this script doesn't belong to any one specific module or component I can't create a test catalog for it in the application hierarchy. I also realized that if I created a test plan from the three test catalogs with VA01, VL01N and VF01 I wouldn't be able to execute them individually because the scripts share Import and Export variables. What is the Best Practice for creating and storing multi-transactional, cross-component tests that simulate business processes?
Secondarily, is there a forum dedicated to eCATT, TestWorkbench or SAP automated testing? If not, which forum would be the best place to post these testing related questions?

Ben,
there are effectively two approaches:
1. Find the "lowest common denominator" - if you have a master script that calls scripts from various sub-components of SD, place the master script in SD (top level)
2. Try to establish the "lead activity" in your master script - ask yourself the question "How would I describe this test case in one sentence?". Then try to classify the master script according to that.
Both approaches have advantages and disadvantages.
There is, of course, a third possibility. If you have real baseline tests that test business processes that run right through everything, you could put the catalog at "SAP" level in the application hierarchy.
Feel free to keep posting your testing questions here!
Regards
Jon.

Problem in clicking the button - eCATT

Hi Friends,
I had created one script using eCATT. In that script, one button need to click in one screen. The click was happening fine and script was running fine in one machine but the same script was not running in another machine. I feel the problem is cliking of the button has not happening properly. how to resolve the issue. may be the machine is too fast.
Can you please any one guide me on this.
Regards,
Mahendra

Hi mahendra,
As you have already mentioned that version problem exists,
we need to record the two system higher and lower release and make versions, so that script works fine in all the releases.
regards
vinay
p.s@
Version Management for Test Scripts
On the eCATT initial screen or the test script editor, choose Utilities Version ® Management or .
On the Version Management screen, you can specify the same versioning data for a test script as you would on the Attributes tab of the test script. However, we recommend that you use the version management screen because you can see the data for all versions simultaneously.
On the Versioning Data tab, you specify the data that is used to determine which version of the test script should be selected for execution.
This data is used by eCATT to determine which version is to be executed when the test script is referenced by a test configuration or a REF command. eCATT inspects the target system at replay time and stores the software component, release, and patch level of the target system in the log. It then compares the target system data with all the versioning data of the test script and selects the version that matches.
·        Software Components. For example, SAP_BASIS. You can list several software components. If you use the F4 help, you can select the actual software components from the maintenance system.
·        Releases and Support Pack Level. You can specify the releases (for example, 620) and patch levels for which the test script is valid. If you use the F4 help, you can select the actual values from the maintenance system.
¡        You need not specify the patch level.
¡        If you specify a particular combination of software component, release, and patch in one version, that combination cannot be specified in another version. Backup versions are the exception to this rule.
¡        In one version only, you can enter an asterisk (*) in the Release field. This version will be used if no other version has release data that matches that of the target system.
·        If you enter R(for required) in the Relevance field of a row, then the validity of the version is always determined by the entries in the row. Alternatively, you can enter O(for optional). This is useful for specifying several combinations, only one of which need exist in the target system for the version to be valid.
On the Version-Dependent Attributes tab, you can edit the following attributes:
·        Title
·        Backup u2013 select this to exclude the version from the version search.
·        Status u2013 select to allow the test script to be executed as part of an automated test.
·        System Data Container u2013 for the maintenance system.
·        Test System u2013 the maintenance system.
Simulation
You can choose to simulate the version selection process. This enables you test that the versioning data is correct by seeing which version is selected for the specified target system.
The simulation examines the target system. It then compares the information from the target system with that of the versioning data of the test script. First the backup versions are eliminated from the search and then software components are compared. Next the release information is compared. Specific entries (for example, 620) take precedence over asterisks (*) which in turn take precedence over empty fields. Finally, the patch level is assessed. Again, specific entries take precedence over asterisks which in turn take precedence over empty fields.
Creating a New Version
You can create a new version based on the selected version. The new version is identical to the old but with the backup flag set. You can then modify the version information.
Deleting a Version
When you try to delete a version, eCATT checks to see if the test script is used by another object (for example, a test configuration). You will only be able to delete a version if the test script is not being used, or if the backup flag of the version is set.

Ecatt multiple line items

Hi Gurus,
i am creating ecatt with TCD recording. My requirement is if i record a sales order with one line item can i use the same ecatt for multiple line items.
for example if i create a test script z_va01 in this i record a sales order having one line item. For this i created test data and configaration. Can i use same ecatt to create a sales order having multiple line items.
Thanks in advace
anil

Hi guys,
I know it has been a long time since this thread was opened, but I'm facing with the same problem.
I created the sales order with SAPGUI REC, and added a loop for line item creation and schedule line creation.
*LINE ITEM NUMBER
DO ( V_LNIT_NO ).
SAPGUI ( VA02_2010_STEP_2 ). --> Adding line item
V_LI_ROW = V_LI_ROW + 1.
ENDDO.
And i amended the line item selection Guielement ID - (Changes are in bold)
'wnd[0]/usr/tabsTAXI_TABSTRIP_OVERVIEW/tabpT\02/ssubSUBSCREEN_BODY:SAPLJ3AD:2930/ssubSUBITEM_L2:SAPMJ3AS:2001/tblSAPMJ3ASTCTRL_LINE_ENTRY/ctxtJ_3ASZDI-MATNR[3,<!V_LI_ROW!>]'
so that the loop will make the line item selection to the next line.
My requirement is to upload the data through a excel file, so I created a test configuration with the relevant variables. But the data from the excel line wont populate the loop data, it only repeats the data from the same line over and over again.
How can I fix this? Please help.
Ps - I have tried to make the the MATNR_D to a table by adding [], --> MATNR_D[] - Table. And it becomes a <INITIAL>, and by clicking on the value column cell, it goes in to parameter I_MATNR (I defined this)
and you can add Parameter 1, 2, 3 etc and within the parameter you can add table-line. I read that this is the solution but, the variable is not recorded on the excel sheet as a column. Please help

Importing internal table data from FM to eCATT test script

Hi all,
I am working on Workflow project where by i need to post invoices related to purchase orders sent as scanned imaages. Incase all the data in the incoming invoice(scanned) is correct then i am using BAPI_INCOMING_INVOICE_CREATE to post the invoice.
But when the data is wrong, i need to give the user MIRO transaction pre-populated with the invoice details so that he manually corrects them(after verification) and posts the invoice.
I understand MIRO is an ENJOY transaction hence BDC doesn't work properly(i have tried with all kinds of options on recording and the problem comes incase of multiple POs) hence i choose to use eCATT.
The recording worksfine but my real problem is the PO data (multiple PO details for same invoice) is in table form. In all my previous objects related to eCATT we used to upload the file, hence no problem of importing tables.
But now as i'll call this test script from a function module which has all the POs in the form of internal table, i need to import this into my test script.
Please any body tell me how to proceed in this case or please suggest me a better a way to record the MIRO.
Thank you,
Lakshmi Narayana.S

Hello Raj,
First of all thank you for your inputs.
Yes, I know about Parking an invoice. even i am using it in some scenarios.
If everything on the invoice matches with the values in SAP then i am posting it using BAPI invoice_create also.
But for some scenarios like if the PO on the invoice doesnot match with actual PO then i need to create a work item in the Accounts Payable user's inbox and he will change invoice data manually (after getting confirmation and correction) and post it using MIRO.
Here i need to pre-populate the MIRO with the invoice data so that he can correct and post it.
Hence i was trying to write a BDC and as MIRO is an Enjoy transaction i thought writing a BDC is not a good idea (i tried writing BDC but had problems) hence i am using eCATT.
Hope i am clear about my problem. Any inputs to solve this are welcome.
Thanks,
Lakshmi Narayana.S

Using mercury test scripts in eCATT

Can anyone tell me if its possible to use the test case built in Mercury QTP be used as eCATT test case to run the test. If thats possible wats the way to use them. All along i hav been using Mercury to Test Sap application now i need to build the test scripts in eCATT for the same. Can i make use of the test scripts built in mercury
is it possible to use the test scripts built in the older version say 6.2 of mercury used in 4.6C or 4.7 os SAP eCATT
can i atleat get the scripts into CATT and then migrate it to eCATT.

Hello,
Please post your question in the WAS forum.
SAP NetWeaver Application Server
thx,
E.T.

Urgent help need on eCATT script

Hi
How to use eCATT script tool with transaction SECATT.
urgent please help.
regards,
R K

Hello Rao
If you are using a "normal" transaction without any controls (like ALV lists, trees) then you can use the recording pattern TCD REC (TCD (Record)).
In transaction SECATT give a name for your test script (e.g. Z_XD01 or Z_CREATE_CUSTOMER). Within the test script choose pattern TCD REC and enter the transaction you want to record (e.g. XD01).
After finishing the recording you will see the following line in the eCATT editor:
TCD ( XD01 , XD01_1 ).
Meaning:
- TCD = recording pattern
- XD01 = recorded transaction
- XD01_1 = eCATT interface for the transaction
Next double-click on the eCATT interface name (here: XD01_1). Next to the editor you will see the interface displayed as tree and as ALV list. Here you can parameterize your transaction.
Please note that you should preferably use the highest available SAP release for eCATT recording. If, for example, your business system has release 6.20 and you have a 6.40 system available record the eCATT on the 6.40 system via RFC.
Regards
Uwe

ECATT Script with SAPGUI Commando works in consolidation but not in prod.

Hi experts,
I created a eCATT script with commando SAPGUI Rec. In our consolidation system it works fine but when I try to let it run in production it is not working. User scripting is enabled (in options and in rz11). I am starting the script, the production system is getting opened but afterwards there happens nothing anymore. Also the scriptingsign in the bottom right corner is not active.
When I am running a script with TCD Rec, it works fine in production. Is there a difference between settings for scripting for TCD Rec and SAPGUI scripting? Do you have any idea which kind of influences there could be that make this difference between TCD Rec and SAPGUI Rec scripts?
Best regards and thank you in advance!
Jan

Hello,
Ideally we should not run the ecatts in the production system as this would hamper the system environment or change systems.
Also check in RZ11 enter sapgui/user_scripting , here the values for the last three parameters are set to TRUE.
Thanks & Best regards,
Ajay

Testing Webdynpro Application using ECATT

Hi
all
I am going to test webdynpro Application using ecatt.For this in se80 I selected the
existing component(z component which was created by me) and i selected the application of that component and right clicked and selected START ECATT RECORDING and i have given the test cript name at that i have got one error USER ECATT_HTTPDoesnot exist. How to resolve this problem.
Please give me the soulution regarding this.
regards
venkat

Hi Venkatesh,
Before you can start recording any webdynpro application make sure that the below settings are done in the ecatt system and the target system , for further information refer ecatt documentation.
Create User ECATT_HTTP in the eCATT System
The administrator in the eCATT system must create a user called ECATT_HTTP(with a password). The user requires no special authorization but must be a system user (in transaction SU01, display the user and choose the Logon data tab. Under User Type, select System).
Activate the Service ecatt_recorder in the eCATT System
       1.      In the eCATT System, start transaction SICF and navigate to the service ecatt_recorder.
       2.      Double-click on ecatt_recorder.
       3.      On the Logon Data tab, enter the user ECATT_HTTPand the password.
       4.      Choose Save.
       5.      Select ecatt_recorder and choose Service/Virtual Host -> Activate.
Activate the Service ecattping in the Target Systems
Java System
       1.      In the Visual Administrator, choose Server ->Services -> Deploy.
       2.      On the Runtime tab, select Application.
       3.      Select ecattping.
       4.      Choose Start Application.
ABAP System
       1.      In the target system, start transaction SICF and navigate to the service ecattping.
       2.      Select ecattping and choose Service/Virtual Host -> Activate.
Thanks and Regards,
Balaji.D.N
Edited by: Balaji DN on Dec 31, 2008 12:04 PM

ECATT issue in Tcode MIGO- High priority

Hi ,
We are facing an issue in eCATT for Tcode MIGO in MM.
Everything went on well earlier. All of a sudden an error occurs as"Programming error. Data already aggregated". I asked my MM guy to check with his data. he says the MIGO is fine when ran independantly as aTcode. Thi serror occurs only while running thro' eCATTs. I would request someone to respond on this ASAP as we are stating our UAT today.
Sudha

Hi Sudha,
Even I am getting exactly the same error while running the script in Ecatt for the Tcode - MIGO.
(Error : Proramming error : Data already aggregated)
How did you resolve the error? Please help me in solving this error.
Regards,
Sachin Maheshwari
9881154030

Impact Of eCATT Version Upgarde From 3.1 To 3.2

Dear All,
There is a query related to version upgrade of eCATT from 3.1 to 3.2. The Web Application Server is 6.20 with Patch level 46.
What will be the impact of the version upgrade of eCATT to the already existing scripts which were developed in version 3.1. Will there be any changes? If so, please give the details.
Thanks & Regards.

Hello Jonathan,
Thanks for the reply. Yes the solution manager is getting upgraded from version 3.1 to 3.2. So I just wanted to know the impacts of this upgrade on the existing scripts. Will they run smoothly as earlier.
Again with this version upgrade, what new features will be available into eCATT.
Thanks & Regards.

The tool for testing developed system

We have already developed a system base on WebAS.Is there some test tool for the developed system such as J Unit in Java?Thanks.

If your intentions is to test user interfaces or scenarios eCatt is the best choice. If you want to ensure code quality ABAP Unit and Code Inspector are suited well.
http://help.sap.com/saphelp_nw04s/helpdata/en/10/6d1c370c468b7be10000009b38f936/frameset.htm
Best Regards
Klaus

Ecatt vs. Manually entered transactions

Hello
We are currently performance testing and we are thus creating a lot of transactions using eCATT - e.g VA01.
My question is now: why is there a difference in response time when creating one VA01 with the eCATT and creating one VA01 manually (with exactly the same line items, customer etc.)?
And finally: is there a ratio that we can apply to compare eCATT generated VA01s with manually entered VA01s?
Thank you very much.
Cheers
Tajs

Hi,
ECATT is a automation tool meant for functional testing in SAP. It comes with WAS.
QTP tool which is a third party tool for automation testing. The language used here is VB Script.
The only drawback with ECATT as of now is that it can execute web based SAP transactions except WebDynpro.
If the testing of SRM, CRM etc is involved, one is forced to use QTP.
QTP takes the wrapping of ECATT and executes in SAP.
SAPGUI based transactions are involved in testing than ECATT is the best tool to be used.
And if web based transactions are also involved, forced to go for QTP.
I think it would help you to some extent
Edited by: Vagdevi on May 18, 2009 5:48 PM
Regards
R
Edited by: Vagdevi on May 18, 2009 5:48 PM

ECATT benefits for ABAP developers

Dear All,
I'm new to eCATT, but have gone through eCATT tutorial successfully.
My question is not about how to use SECATT transaction rather I'm interested in using eCATT from a ABAP developer point of view.
Since, functional testing is main responsibility of functional consultants, therefore, how can ABAP consultants use eCATT for their advantage? I've heard that eCATT can also be used for uploading data, is that right? What else can I achieve with eCATT other than testing SAP transaction? It'll be helpful if you can post an example describing that how you used eCATT for your advantage.
Have a nice day!
Hashir Ahmed

Hello Hashir,
As you mentioned we can use eCATT created to setup the customization and master data required for the process to be tested manually within less time , this saves a lot of time as more time is required to setup the masterdata for the process.
Also we can use eCATT during the support pack test , perform regression runs of the earlier functionality to check whether the basic functionality is working fine after the enhancments have been implemented.
Overall the eCATT saves a lot of time of manual testing.
eCATT can be used to test web applications aswell apart from SAP R3 transactions.
eCATT supports the integration of the third party tool like qtp , testpartner.
Thanks & Best regards,
Ajay

ECATT: Parameterise the ID of a guielement

Similar Messages

Maybe you are looking for