eCATT Scripts Creation Non-User Interface Mode & Rename, Copy, Delete, Upload, Download eCATT Objects(PART VII)

[Former Member]

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 are explained in detail.


In Part VII, creation of eCATT Scripts using Non-User Interface mode will be explained along with the details of Copy, Rename, Delete, Upload and Download of eCATT objects. In the subsequent Part, tips & l inks of eCATT will be covered.

Key Features Of Non-User Interface Recording Mode:

• The non-user interface can be used for testing back-end R/3-specific modules, such as function modules and BAPIs.
• 
  
• It should be the preferred driver for interface tests in the mySAP environment.
• 
  
• It is fast, efficient, and suitable for load testing.
• 
  

Steps For Recording Using Non-User Interface Recording Mode:

1. 
   
2. Transaction SECATT.
3. 
   
4. Give the name of the Test Script(TS) in Test Script input box. The Version input by default is with value 1.
5. 
   
6. In the Attributes ->General Data Tab, the value of the component will be BC-TWB-TST-ECA for eCATT.
7. 
   
8. In the Attributes ->General Data Tab, the values of the SystemDataContainer should be given which contains all target systems with RFCs on which the script will be either executed or recorded & in the TargetSystem the name of target system (e.g. recording R/3 server) should be mentioned.
9. 
   
10. Click on the Pattern (Ctrl+F6) button from the application toolbar.
11. 
    
    

1. From the Command dropdown, select FUN. In the Function Module give the name of the function module/BAPI, which needs to be tested. Click on enter. The Interface name will automatically appear (E.g. Here BAPI_MATERIAL_SAVEDATA is used). Click on enter.
2. 
   
   

The FUN with the function module/BAPI name along with the command interface will be inserted into command editor.

1. Double click on the Command Interface (e.g. BAPI_MATERIAL_SAVEDATA_1) from this FUN syntax in the command editor. On the right side, the command interface will open in a window. The command interface will have all the IMPORT/EXPORT/TABLES/EXCEPTIONS parameter of the given function module/BAPI.
2. 
   
   

1. Under the IMPORTING/EXPORTING/TABLES/EXCEPTIONS node, all the import parameters, export parameters, tables & the exceptions belonging to that function module/BAPI are present. These parameters can be parameterized.
2. 
   
   
   If the function module or BAPIs are called in the ABAP Program then the way the values are passed to those parameters, similar ways values will be passed here in terms of Parameterization. The declaration of these parameters will happen at the Parameter List as either Import/Export/variable.
3. 
   
   

The output message variables, like the other recording modes, can be captured from the Exporting node.


     

1. All the parameters needed for the execution of the function module/BAPI will be declared in parameter list and then parameterized.
2. 
   
   

1. In the current example, BAPI is used for Material create and saving this data. Before this a unique material number is generated by system using another BAPI. This is written in ABAP-ENDABAP block. After the number is generated, this newly generated number is assigned to a variable. As import and export parameters cannot be used in inline ABAP code. So the variable is used. This variable is then passed as import parameter to BAPI, which is to be tested via this recording.
2. 
   
   

1. Once the parameterization is done. The script is ready for execution. There is no specific Start Options mode available for Non-User Interface mode at execution time. It always executes in Background mode.
2. 
   
   

1. If the recording is error free, then success log will appear. And if there is any error in recording of the transaction and its replay then error log with details will appear.
2. 
   
3. Analyze the generated log (weblog Part VI). Following is the log generated for the example mentioned here. It shows Import, Export parameter along with the execution mode and time taken for each of the individual step and complete execution.
4. 
   
   

1. Inline ABAP code is also shown in the log. It shows the results also.
2. 
   
   

1. The function module/BAPI is also shown in log. The Importing/Exporting parameters along with the message generated.
   
   

1. After the confirmation of error free recording, one can go ahead with the preparation of TD, TC for the TS.
2. 
   
3. In SECATT 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 appear as ECATTDEFAULT in the Variants tab. Add multiple variants, as per requirement in the Variants tab. Test Data is independent of test script. Hence can be reused wherever required. (Weblog Part IV).
4. 
   
5. In SECATT transaction using Test Configuration (TC), the TD & TS can be linked together on the Configuration tab. On the Variants tab, using Variant Maintenance Assistant required variants values from TD could be linked to TC. (Weblog Part IV).
   
6. Finally the TC can be executed from SECATT directly by giving the required variant name at runtime. (Weblog Part IV).
7. 
   
8. The TC is used in managing the scripts in plans/packages using SCAT transaction. (Weblog Part V).
9. 
   

How To Copy, Rename & Delete eCATT Objects:

1. 
   
2. One can copy all the eCATT Object i.e. Test Configuration, Test Script with Version, Test Data & System Data.
3. 
   
4. Transaction SECATT.
5. 
   
6. Click on Copy Object (Ctrl+F5) icon from the application toolbar.
7. 
   
   

1. Copy dialog box appears with the copy detail for the eCATT Object whose radio button was selected on SECATT.
2. 
   
3. For Test Configuration copy, give the name of the new TC and click on Copy button. The new test configuration will be ready.
4. 
   
   

1. Similar way, for Test Data and System Data, give the new names and click on Copy button.
2. 
   
   

System Data Copy-

1. For copying Test Script, system gives one Version input field on Copy dialog box. If this field is left blank then all the versions are copied to new name. Otherwise only the specified version is copied.
2. 
   
   

1. Rename eCATT Object: Similar to copying the eCATT objects, renaming can be done. On the application toolbar of SECATT transaction, click on Rename Object (Ctrl+F6) icon from the application toolbar.
2. 
   
   

Depending on the eCATT object selected, the Rename dialog box will appear. Give the new name and click on Rename button. The object will be renamed.





Similar ways all other eCATT objects can be renamed.

1. Deletion Of eCATT Objects: Similar to Copying & Renaming, all the eCATT objects can be deleted. Click on Delete Object (Shift+F2) from the application toolbar of SECATT transaction.
2. 
   
   

Confirmation Prompt dialog box will appear. Click on Yes for the deletion of object.





There is no dependency on objects for deletion. Meaning deletion of TC won’t affect the TD & TS inside it. In case of Test Scripts deletion, to delete specific version mention it in the transaction. If the version field is left empty, all the versions are deleted. Similar way all the other eCATT objects can be deleted.

How To Download eCATT Objects:

1. 
   
2. eCATT objects can be downloaded in XML & XSD format. These files can be further uploaded to any system. Hence the reuse of objects and their transfer amongst the R/3 system is facilitated. All the objects i.e. Test Script, Test Configuration, Test Data & System data can be downloaded via SECATT transaction. For a script to work successfully, the entire linked object should be present along with it like System Data, Test Configuration & multiple Test Data containers. This linking of objects can be known and the entire related object could be downloaded in one shot.
3. 
   
4. Transaction SECATT.
5. 
   
6. Give the name of Test Configuration or Test Script or Test Data or System Data, which needs to be downloaded.
7. 
   
8. Menu Goto -> Reference List.
9. 
   
   

1. One List Of Referenced Objects screen comes. Object Type & Object Name automatically appears depending on the selected eCATT object on SECATT screen.
2. 
   
   

1. Click on Execute (F8) button from the application toolbar. List of referenced objects will appear.
2. 
   
   

1. Click on Download All Objects (F5).
2. 
   
   

All the objects from the referenced list will be downloaded at the path given in the Browse For Folder dialog box. Click on Ok.





The files will be downloaded at the given destination in XML XSD format.






Similar way other eCATT objects can be individually downloaded.

How To Upload eCATT Objects:

1. 
   
2. eCATT objects i.e. Test Script, Test Data, Test Configuration as well as System Data can be uploaded via SECATT transaction from the XML, XSD files. The prerequisite is that both the XML & XSD files should be present in the same folder.
3. 
   
4. Transaction SECATT.
5. 
   
6. Menu eCATT Object -> Upload.
7. 
   
   

1. Select Files For Upload dialog box appears. Select the file and click on Open button.
2. 
   
3. Change eCATT objects to be uploaded window appear. Select the eCATT object, give the target object name if not present & click on Enter. The object will be uploaded and directly taken to SECATT window.
4. 
   
   
   In case of Test Script, the Target Version (TV)

number can be given.



This way multiple objects can be uploaded.

System Data Container Upload/Download:

When uploading or downloading system data containers for copying to another system, the name of an RFC destination remains unchanged in the RFC Destination field. However, in the new system, this name might not exist or might be that of a different RFC destination. In this case, RFC destination needs to be maintained.