Skip to Content

eCATT Scripts Management Via Test Workbench (PART V)

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 Part III, SAPGUI recording mode of recording is explained in detail. In Part IV, the parameterization, creation of Test Configuration,Test Data Container, System Data Container are explained in detail. In Part V, the management of eCATT Scripts via Testworkbench will be explained. In the subsequent parts eCATT Logs & other details of eCATT will be covered.
Why eCATT Scripts Management Is Required By Test Workbench By SCAT:
  • eCATT scripts can be very well executed via the transaction SECATT by which the scripts are created. In SECATT, the script execution can happen at Test Script (TS) level or Test Configuration (TC) level. At test script level execution, the data may need to be changed depending on the behavior of transaction(s) in the script. This change will override the default recording data of the script. If the script recording is error free then change of the data at TS level is not recommended. Hence execution of the script via TC is adapted. In TC, the data is changed at variant level, which are picked from Test Data (TD) Container. Changing data in TD doesn’t affect the default recoding time data i.e. ECATTDEFAULT. Now even if the execution can happen via TC, then also clubbing of TCs, which are related depending on a series of functionality or the function module or location against which the test case is being executed, is not possible via SECATT transaction.
  • Moreover one has to maintain the log IDs of the scripts being executed via SECATT. As script executes multiple times, the logs are stored against that script. So which log has generated during the final regression testing time is difficult to make out.
  • Hence for the Regression Test, the requirement is that somewhere the log IDs should be present along with the scripts, which are as a result of the test carried out during final testing. These log IDs will be available for future use. So all the requirements of grouping the scripts on some defined conditions, availability of log IDs for future usage will be fulfilled by Test Workbench SCAT Transaction.
How Scripts Can Be Managed In Test Workbench:
  • Test cases can be managed in test workbench via Test Catalog, Test Plans & Test Packages. Also with the Test Workbench test status can be analyzed. Test status is in terms of traffic lights for eCATT logs.
  • Test Catalog – A Test Catalog is a set of test cases in a hierarchical hypertext structure. To be able to use the test catalog to generate test plans, one must put it in the SAP Application hierarchy. One can create test plans across several test catalogs via the SAP application hierarchy. This procedure allows creating a lot of small test catalogs, which are easier to maintain than one large test catalog.
  • Test Plan – A test plan is a set of test cases, which must be tested, in a particular period for a particular purpose. The relevant test cases can be divided among several test catalogs.
  • Test Package – A test package is a person and period-oriented view of a test plan. It contains all tests, which a tester is to perform in a specified period.
  • After a test, the tester sets the test case status, e.g. ‚Pass‘ or ‚Fail‘. one can get an overview of the status of all test cases of a test plan with Status analyses.
  • image
Creation Of Test Catalogs:
  • Transaction SCAT or Tools->ABAP Workbench->Test->Test Workbench->Test Organizer->Manage Test Catalog.
  • Click on menu Environment->Manage Test Catalog.
  • Click on Create (F5) icon from the application toolbar.
  • Test Catalog Information window appears.
  • Give the name of System Data and Target System in the eCATT section. System Data container should contain the RFC for the Target System on which the script will execute.
  • In Test Catalog Header Data section give Title. The title is the name of the catalog by which it will be referred in the Test Plans.
  • In the Responsibility section, Name contains the logged in user name by default.
  • Click on Save (Ctrl+S) from the standard toolbar.
  • image
    The Test Catalog is created. Now the Test Configurations need to be added to this test catalog.
  • Select the Test Catalog created in step 8 and click on Change (F6) icon from the application toolbar.
  • Under the Structure, name of test catalog will appear.
  • Select Test Catalog name and click on the button As Subnode (F5) from the application toolbar.
  • image
  • Insert Nodes window appears. Here we are adding the Test Configurations to the test catalog. So select the second radio button of Test Case. Give the value from the dropdown list as E eCATT Test Configuration.
  • In the Test Case Key, click on F4 help. Select the Test Configurations from the system. As the grouping of the scripts is on the basis of the location against which the test is carried out, so all the scripts, which will be specific to this particular location, should be selected.
  • In the Variant Selection, select the Special Variant radio button. Click on F4. Now in the list shown by system will show only the common variant to all the select Test Cases from step 13. If in case the scripts are selected which don’t have common variant names then only the variants of first test case appears in the list.
    • Without Variants – Only with ECATTDEFAULT.
    • All Variants Including Default Variant – All the variants including ECATTDEFAULT variant.
    • All Variants Excluding Default Variant – All the variants excluding ECATTDEFAULT variant.
    • Special Variants – Only for the selected variants from the list, which are common to all the selected test cases.
  • Select the variant for the location against which testing is carried out and press enter. All the selected scripts along with the variant name will appear under the Test Catalog name.
  • image
  • Click on Save (Ctrl+S) button from the standard toolbar..
  • In order to use the test catalog in Test Plans, test catalog must be present in SAP Application Hierarchy. To achieve this, click on button Library (Ctrl+F12) from the application toolbar or click on GOTO menu -> Library.
  • image
  • Select path as follows => Test Organizer Library -> Application Components -> BC -> BC-TWB Test Workbench -> BC-TWB-ORG Test Organizer -> BC-TWB-ORG-CTL Test Catalog. With the Test Catalog selected, click on Nodes (Insert Nodes F5) button from the application toolbar.
  • One small window of Create Link appears. Click on (Find) Test Catalog button. Give the name of Test Catalog created in step 16 in the Description field. The name will appear in the search help output window. Select the catalog and press enter.
  • image
  • One Information popup appears ‘ The two structures are from different mySAP components’. Press Enter. The catalog will be added under the Test Catalog node.
  • Click on Save button from the standard toolbar. Now the catalog is present in the application hierarchy.
  • This way multiple test catalogs can be prepared depending on some defined conditions like different locations against which the testing will be carried out. These test catalogs then can be used for the preparation of test plans.
Creation Of Test Plans:
  • Transaction SCAT.
  • Click on menu Environment->Manage Test Plans.
  • Click on the Create (F5) icon from the application toolbar.
  • Create Test Plan window appears. In the Template, select Application Component Hierarchy. Under the Test Plan & Header Data section, give the Test Plan Title. With the Test Plan Title, the plan will be referred. In the eCATT section, give the name of System Data Container & Target system on which the scripts will execute. Click on Enter.
  • image
  • The system will take to Crate Test Plan screen where the Test Organizer Library is displayed. Here from this SAP Application Hierarchy, select the test catalog. This test catalog is the one whose scripts will be pulled in the test plan and then subsequently in test package of that plan. Scripts from multiple test catalogs can be taken. Select path as follows => Test Organizer Library -> Application Components -> BC -> BC-TWB Test Workbench -> BC-TWB-ORG Test Organizer -> BC-TWB-ORG-CTL Test Catalog. Select the scripts from single or multiple Test Catalogs as per the requirement.
  • image
  • Click on Generate (F8) button from the application toolbar. After the plan is generated save it.
  • image
    Test Plan is ready now. One can prepare the Packages from this plan by some defined conditions like scripts of foreground execution, background execution or different tester or different target systems at execution time.
Creation Of Test Package:
  • Select the test plan created in step 6 above. Click on Test Packages (Ctrl+F9) button from the application toolbar.
  • image
  • Test Organizer – Test Package Management screen comes. Click on Create Test Package button.
  • image
  • It will display all test catalogs under that test plan. Select the scripts from the required test catalogs depending on the condition on which that package is planned. After selecting the scripts, click on Generate (F8) button. The Create Test Package window for title appears. Give the name of the package in the title. By this name the package will be referred always. Click on Enter.
  • image
  • Once the package is prepared, select the package name and click on Status button for refresh. Once the refresh is done, the right panel will show the number of scripts against that package under the Error/No Result/Ok columns.
  • image
    The package is also now ready. This way multiple packages can be prepared which will involve all the scripts of the plan in totality.
Execution Of Test Cases Series Via Test Workbench:
  • Test Cases can be executed via different ways at different levels in test workbench system. Test Cases can be executed at Test Catalogs level/Test Plan level or even at Test Package level.
  • The scenario depicted here is by creating a pool of test cases in Test Catalogs. Then from those test catalogs preparing Test Plans depending on some defined conditions. From these plans again preparing Test Packages. And finally executing these Test Packages which give the transparent picture of how the testing was planned and carried out.
  • So transaction SCAT.
  • Click on menu Environment->Manage Test Plans.
  • Select the Test Plan, which needs to be executed.
  • Click on Test Packages (Ctrl+F9) button from the application toolbar.
  • Select the package. Before the execution, the status in traffic light for each of the script will be untested.
  • image
  • For the mass execution of the complete package, select the package. Then click on Automatic Test button from the application toolbar.
  • Test Case Selection window appears. If in case all the scripts need not to be executed at a given time, then select the required once. By default all the scripts under the package are selected for execution. Click on Enter.
  • One window with title ‘Start Options (eCATT Mass Start)’ will appear. Select the following options –
    • Error Behavior – S No termination, continue with next script.
    • System Data – Name of the system data container, which contains the Target System.
    • Target System – Name of the server on which the execution will happen.
    • Select the Log Display check box.
    • Select the Status In TWB check box.
    • In TCD section of window, select N – Process in background, synchronous local.
    • In SAPGUI section of window, select following options –
      • Procg Mode SAPGUI – S Synchronous GUI Control
      • Error Mode for SAPGUI – C Continue (Continue on Any Error)
      • Stop When – N Do Not Stop
      • Close GUIs – R Close Generated Sessions After REF
    • Click on Execute button.
    • image image
  • On execute button click on Start Options window, the system prompts for login & password window of Target System. Give the login details and execution of scripts will start in series.
  • Once the execution is completed, the logs are taken back to test workbench and the status of traffic light will either change to green for success or red for error.
  • image
You must be Logged on to comment or reply to a post.
  • Sapna,
    Thanks for such a informative document. It seems each and every step is described in details. The article will help beginners to start using E-catt confidntly…..
  • Sincere and dedicated efforts!!! This article is very informative and useful. Even a layman can use this article to understand eCATT. The flow of the information throughout the article is very nice. The author has taken lot of efforts to explain difficult concept in a simple manner.

    Thanks for such a nice article…Keep it up!!!

    Mangesh Vingkar

  • Hi Sapna,

    This ECATT weblogs covered many interesting features of the eCATT Testing. Well-prepared, very nice and helpful assistants. Good concept even for autodidactic learning.
    Appreciate your sincere dedication and determination towards work.
    Again, very clear and well-written tutorial, well chosen example.


  • Hi! SAPNA,

    Thanks a lot for the GREAT work on eCATT. It is very useful for me cause I didn’t attend any training course on eCATT. I have no clue how eCATT works. But I started picking up some skills by browsing your blogs.

    SAPNA, I have already posted the following question on the forum, however, no feedback from any experts yet. Would you mind help me out ? THANKS in advance for your help.

    I have created a Test Package and assigned Tester to each Test Case. e.g.Data Entry Clerk to Test Script A, Approver to Test Script B.

    However, when I run the Test Case in the Test Package, the system always logon as user “ALE-BATCH” and run the Test Scripts A and B.

    Is it possible to logon as the Tester and run the Test Script ? E.g. logon as Data Entry Clerk and run Test Script A, then logon as Approver and run Test Script B ?


    • Hi Kin,

      To be very specific to your case, you created one package and assigned two scripts to this package. You want these two scripts to run from two different IDs. And you have gone for mass execution for your package.

      To execute in expected way, following steps may help you –
      1. Create a package only for Data Entry Clerk.
      2. Create another package only for Approver.
      3. Your RFC connection must not be trusted so that it can ask always user ID & password at the time execution.
      4. Now ask Data Entry Clerk to execute his package. At run time, system will ask user ID & password. So as expected, the scripts in this package are getting executed by the planned tester.

      Repeat the above steps for Approver.

      Hope this helps you.

      Sapna N. Modi

  • I Created a test Package and saved it. Again I went to the TEst package and saw, I could not see the test cases which are assigned to Test Package. It should suppose to show the test cases and the satus. But I could not see that. What could be the reason for not displaying the test cases ?

    – Ravindra Babu

  • Can we create test plan with out creating test Catalogs? if yes how can we run the test scripts?
    Test Cases can be executed via test plan in test workbench ???

    i have created test plan with out test catalog but i don’t know from where do i need to select the test scripts?

    When I tried creating the test catalog it’s throwing a message i.e. “you are not authorized to use transaction STWB_1”.

    Please suggest me on this …………its urgent

    • Usually we create the test Catalog first and then choose the test scripts needed to form as a test plan.

      Once test Plan is created ,press the execute button and it will execute all the test scripts in the the plan.

      Please reach SAP-Basis team to get the access of STWB_1.

      • thanks for the response,

        client do not want test catalogs to be created they want me to create test plan directly using solman,they mailed me saying this hwat does it mean could you pl explaind it?

        although we do not want test catalogs as stated the test plans are created from the Solar structures not Catalogs which in turn have the eCATT test configuration packages loaded on the test cases tab.

        the solution manager variation where the plan is generated from test configurations loaded into the SOLAR02 Test cases tab.?