eCATT Scripts Management Via Test Workbench (PART V)
Рейтинг: / 358
Автор Administrator   
20.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 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.

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.

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.

  • 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.

  • 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.

  • 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.

  • 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.
  • 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.

  • Click on Generate (F8) button from the application toolbar. After the plan is generated save it.

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.

  • Test Organizer – Test Package Management screen comes. Click on Create Test Package button.

  • It will display all test catalogs under that test plan. Select the scripts from the required test catalogs depending on the ondition 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.

  • 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.

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.

  • For the mass execution of the complete package, select the package. Then click on Automatic Test button from the ation 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.


  • 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.

 Sapna Modi is a Software Engineer.

Просмотров: 13430

Коментарии (14)
Thank you for this nice step by step for SAP test case, 
Please do you have file with data for more data. 
Thank you 
my email: Этот e-mail защищен от спам-ботов. Для его просмотра в вашем браузере должна быть включена поддержка Java-script
Hi Sir, 21:17 23 декабря 2010 г.
The purchases I make are etnilrey based on these articles.
Early, 17:44 17 декабря 2012 г.
DD4Jx2 khzzohcuhqrx
azjquddlo, 13:51 18 декабря 2012 г.
The catablog_show_items() fuictnon has many parameters that you may set to filter your catalog results. But first I want to make sure you are implementing CataBlog correctly.The template fuictnon, catablog_show_items('Cat 1'), is meant to be placed inside your theme's template files, such as sidebar.php or page.php.The Shortcode, [catablog category="Cat 1"], which offers the same parameters as the template fuictnon, is meant to be placed inside the content of a post or page you edit in the Admin section.You may read more about these parameters at the displaying your catalog in posts documentation page. Keep in mind that the Shortcode does not care what order your enter your parameters, but the template fuictnon requires that parameter be implemented in the correct order.
Cassio, 19:25 18 декабря 2012 г.
XaQJp5 mbhyclfzuyph
ocyzrbhh, 10:18 19 декабря 2012 г.
OMMF9E , [url=http://bkbishshltmm.com/]bkbishshltmm[/url], [link=http://vmkjigzqneeg.com/]vmkjigzqneeg[/link], http://vpaormltgigu.com/
cscgtcoifqv, 10:46 21 декабря 2012 г.
Thank you for the compliment. I use the fwolloing code for example on the industial page: [catablog category="Industrial"]. Then when you click on a single product it shows the single template.That all works fine. But what I need is for the overview page to sometimes have a price and sometimes not have a price. So for example when adding a product into the categorie industrial , it should show the price and therefor use the template for a product with price. But when I add an item to, for example the categorie more info , i would like it to show use a different layout for the overview and the single view. so no price is shown and also the background of the layout is different.
Yasser, 13:27 21 декабря 2012 г.
owdpU7 dsjvyirmigby
nfjqcirzj, 02:10 07 января 2013 г.
bQnUVm rkcinfvmnjzu
hobwvvdl, 02:11 07 января 2013 г.
D9fXVg lstrcxkuucnr
rejlyat, 02:11 07 января 2013 г.

Последнее обновление ( 27.02.2009 г. )
« Пред.   След. »
© 2019 ProSapSecurity
Joomla! - свободное программное обеспечение, распространяемое по лицензии GNU/GPL.