This action might not be possible to undo. Are you sure you want to continue?
eCATT Chaining, Parameterization, Creation Of Test Data,Test Configuration, System Data (PART IV)
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 chaining, parameterization, creation of Test Configuration, Test Data Container, and System Data Container will be explained in detail and in subsequent parts the management of eCATT Scripts via Test workbench & other details of eCATT will be covered. What Are Parameters: Parameters are export, import interfaces or local variables of a script. Parameter name can be 30 char long. The first letter should be either an underscore or character. Their visibility within the script is same and outside it is of import parameter, export parameter or local variable. The visibility can be set from the parameters list.
ONLY local variables can be used in the inline ABAP block in the test script editor. Import & Export parameters CANNOT be used in the inline ABAP block. Import Parameters (IP): Import parameters are input values to the script. They are passed to the script during execution. They are locally available and test script version independent. Import parameters can hold default value also. Export Parameters (EP): Export parameters are outcome of the test script execution. The result value is passed into the export parameter when the test returns from the test module. They are test script version
&USER. &M01. a local variable defined in one version is not automatically defined in another version. &CLIENT etc. &SYSTEM. automation can be parameterized. &M04. There are special read-only eCATT variables. This is very similar to concept of Constants in Program (Without parameterization) and using variables for those values (with parameterization). They are also used for passing values to and from inline ABAP blocks & are version-dependent that is. &MS3. &YEARA. &LPC. &HOST. &LANGUAGE. &MSN. &M02. &MSX.2 independent. Transaction can be checked without parameterization for errorless recording. input data will be checked and changed at Test Script level. the recording becomes reusable. &MS2. &MS4. &MS1. &SUBRC. either fixed or parameterized or not define. e. Due to parameterization. &MSI. Different sets of data can be passed via parameters and the recorded script can be used again and again. &LOGID. &REFVERSION. are symbolized as follows ± Why Parameterization Is Needed: After recording of the transaction.g. &REFNAE. Once the successful recording is confirmed. &VARID. &MSG. If parameterization is not done than before next execution of automated script. &EXCEPTION. &MST. which can also be used in command editor. System fields can also be used in command editor. &DBSYS. &TIME. They are read-only and are available from SYST structure. &REFLEVEL. &DATE. &M03. &SCRIPTNAME. &OPSYS. &YEAR. Due to . The status of values. Local Variables (LV): Local variables are used in test scripts for calculations. &SCRIPTVERSION. &SAPRL. &YEARB. or to receive export parameters from referred test cases or called function modules.
Hence parameterization is necessary. Screen simulation can be used to edit and parameterize the fields. field check. select the Dynpro whose fields need to be parameterized as Import/Export parameter. TCD Mode Parameterization: If a transaction is recorded via TCD mode. one can clear it. . Using Screen simulation Import parameters. For parameterization. the screen simulation window will appear. if the field has any value. This is the value one needs to parameterize as Import Parameter so that with next run a new set of data will be passed to the recording. Screen simulation icon is present in the command interface of the TCD mode. For parameterization. Click on Screen Simulation icon of the command interface. Select the field value & click on Insert Import Parameter (F6) icon from the application toolbar. Export parameters. and values in the input field can be assigned. Defining Import Parameters: y After step 3. The system will prompt for the login of recording time target system. Fields having mode S (Set) under each dynpro of the command interface contain some value entered during the recording. To delete the default values space characters ( ) can be passed via screen simulation. then the screens can be simulated via screen simulation.3 this the errorless recording time data will be disturbed. Give the login details. And recording becomes reusable.
This way one can parameterize all the import values. y Read field value window appears. Press enter. Give the parameter name & default value in the Field contents there. Last dynpro in the dynpro list just before the MSG node in the command interface contains the output messages and other outcomes. Give the . Export parameter are necessary for chaining of transactions wherein output of one transaction becomes input for other transaction. Follow step 3. Click on Back (F3) button of the standard toolbar. The field with the technical name appears against which the Param. the screen simulation window will appear. Fields having G (Get) as mode are assigned to export parameters. The parameter will be inserted into the parameter list. Select the field and click on the Read field value (Ctrl+Shift+F3) icon from the application toolbar. Export parameters can be assigned for these values.4 y One Maintain field entry window appears for the selected field with its technical name. After step 3. Here export parameters can be linked between the two transactions interacting. Name needs to be given. Defining Export Parameters: y y y The output results of the transaction are assigned to export parameters.
Click on Back (F3) button from the standard toolbar. SAPGUI Mode Parameterization: Defining Import Parameters: Import parameters are defined for the input values given during the recording of the transaction. These values are present under the Processed Screen node of the SAPGUI command interface for the given screen.5 name of the export parameter. After step 3. clear the value of the field. Click on the Check field (Ctrl+Shift+F2) icon from the application toolbar. . Give the value against this field. Follow step 3. This way one can parameterize all the export values. Maintain field check dialog box appears. If the field has already some value. screen simulation window appears. Select the field. Automatically the name will be included in the Parameters list. Name. The check value can be a constant or a parameter value. Defining Field Checks: One can check whether the runtime value of a field is the expected value or not. Give the name of the variable in the Param. If it doesn¶t exist. Click on Back (F3) button from the standard toolbar. it will be created automatically as import parameter in the parameter list. Click on enter. Click on enter.
g. This way multiple import parameters can be assigned & created.e. On right side the command interface will open. The Interface name is automatically populated by system. Defining Export Parameters: Export parameters are used to link transactions while chaining. So the results are captured from Message node under the Processed Screen node using MESSAGEENDMESSAGE command. Click on Pattern (Ctrl+F6) button from the application toolbar. Define this import parameter in the parameter list with the type of the field & assign the default value. From the Command dropdown. select the MESSGAE MESSAGE END MESSAGE option. Double click on the field number. which needs to be parameterized. Export parameter of first transaction becomes the import parameter in chaining. Click on enter. Material Created out of MM01 transaction. Export parameters are assigned to result of transaction. i.6 Double click on the command interface of SAPGUI command from the test script editor from the left side. assign the Import parameter to Value field. . Under the Processed Screen -> UserChangedState node select the State node of the field. e. On the rightmost section.
This way multiple export parameters can be declared. Declare this export parameter in the parameter list. value from one screen can be passed to the subsequent screen. system generated value for an input field on one screen can be passed to subsequent screen.7 The MESSAGE-ENDMESSAGE for interface MSG_1 will be inserted into the test script editor. Passing Values To Subsequent Screen: In SAPGUI mode. After that assign the respective message parameter to the export parameter. The message variable number can be confirmed from the command interface from the right side. Place this block around the SAPGUI command from which the export value will be captured.g. This can be achieved by assigning an Export Parameter to the . E.
Double click on interface from the SAPGUI command in which the parameter to be captured exists. And it can be passed further in same recording to subsequent screens as import parameter. the value will exist. Under the Processed Screen -> Initial State node. in test script editor. Make sure that the Check. Declare this export parameter in the parameter list. There in Value. double click on the number. which appears in square braces. which is to be captured. On the right side. is blank instead of X .8 required value. On the right side. write the Export Parameter name. Chaining Of Scripts: Test case is a series of steps (transactions) involving one business . of the topmost GuiElement branch under which the GuiElement exists which needs to capture. the command interface will open. Under the State node of the GuiElement. And then passing this export parameter as input (import parameters) to subsequent screens. Name & Value will appear.
select REF command. On the rightmost side. Click on Pattern (Ctrl+F6) button from the application toolbar. which is outcome of first transaction. The REF command will be inserted into the test script editor. create a new script. which were assigned. Both the scripts should be parameterized as well. all the import parameters appear under the Element column. These Importing and Exporting node have import and export parameters. Each step is automated and then linked together via chaining so as to complete the business scenario. Double click on the Command Interface of the inserted REF statement in the test script editor. VA01 output of sales order can be given as input to VA02. On the right side the interface will open with the Importing/Exporting nodes. Double click on importing node. while creation of that script. which are related in a way that output of one script becomes input to other. In the Test Script. Transaction SECATT. Chaining mainly involves the linking of script by import & export parameters. The Interface name will be automatically populated. Press Enter. From the Command dropdown. which needs to be linked. give the name of test script. One Insert Statement dialog box will appear. For creating chaining of the scripts. The export parameter. Create two test scripts. E.g. is passed as import parameter to second transaction and so on. . Press Enter.9 scenario.
10 Declare all import parameters in the Parameter section above and assign then in Value column below against the Import parameters. On the right side the export parameters. . The import parameter of chained script is assigned to the respective Importing node element. which were created during the script creation are displayed. Similar ways include other test scripts also using REF command. Assign the import parameters and variables to the Importing as well as Exporting nodes respectively. Declare the variables and assign them to the export parameters. Double click on Exporting node of the command interface. The export of one test script will be assigned as import of the next script using variables.
Give the necessary details like RFC Destination. TD and TC can be prepared. Connection Type. Click on Save (Ctrl+S) button from the standard toolbar. Creation Of System Data Container (SD): System data container contains the list of the target servers. The parameter list of this chained script contains only the import parameters as well as the variables. Description. Once the successful execution of the chained script is confirmed. By giving the default values in the import parameters.11 This ways multiple transactions can be linked together in the final chained script. Using SM59 on source system (where eCATT scripts will be available). execute the script and ensure the correctness of chaining. which can be used at the recording time and/or at execution time. Target systems with their RFCs are mentioned in the SD. Creation of RFC for target system: RFC destination will be created for the target systems. . which will be used as recording time and/or execution time systems for eCATT scripts. create a RFC destination for R/3 system.
After RFC creation. Under the System Data tab.12 In Logon/Security tab. This ensures that every time. Click on Create Object (F5) icon from the application toolbar. in the Attribs tab. On the create screen. the server can be added to the SD list. Hence secure. transaction SECATT. In the System Data input field give the name of SD. login window will be prompted when target system is referred via RFC. give the Title (mandatory) for the SD. For SD creation. . recommended is to mention the Trusted system No . target system NONE is already present.
under the Attributes -> General Data tab in the Header Data section. TD is independent of test script. Add the parameters. Under the Parameters tab. In the Test Data input field. give the System Data Container as well as Target System. By this name the target system will be referred in eCATT. Under the Maintenance System. Transaction SECATT. . Hence once created can be used for multiple scripts. give the name of the target server. Click on Save (Ctrl+S) icon from the standard toolbar.13 Append a new row by clicking Append row icon from the toolbar. On the create screen. give the name of the test data. The parameters name & type must match to that of the script to which the TD will be linked. Under the RFC Destination column. Variants created in TD are linked in Test Configuration. The Instance Description field is automatically filled by system. Click on Save (Ctrl+S) button from the standard toolbar. click on Append Parameter icon and the new lines will be appended in the parameter list. This way multiple target systems can be added to the system data. Click on Create Object (F5) icon from the application toolbar. In the Test System column. Variant values are also maintained in TD. Add the lines to the required number of parameters. Creation Of Test Data Container (TD): Test data containers are used for creation of variants. give Title (Mandatory) and Component (Mandatory). which is present in the SD. select the respective RFC for the target system.
TC is used in scripts management using Test Workbench in R/3 system.14 To create variant. minimum one parameter should be present in parameter list. Creation Of Test Configuration (TC): Test Configuration contains reference to one Test Script (TS). one System Data container (SD) and can contain reference to multiple Test Data container (TD). Give the details of new variant with values. the column titles are Variant. the script can be checked for different sets of data using Variants of TC. One more Advantage of using TC is that for any given script. To add new variants. Click on Save (Ctrl+S) button from the standard toolbar. click on Append Variant icon. Under the Variants tab. Description & after that the parameters from the parameters list. ECATTDEFAULT variant will be present as default. This variant contains values from the Parameters under the Parameters tab. . Hence the errorless recording time data is always maintained in TS. Add required number of variants this way. without changing data at TS level. In turn these variant values are captured from TD.
On the create screen. give the Title (Mandatory) & Component (Mandatory). give the System Data Container. For TC creation. Give the name of TC in Test Configuration and click on Create Object (F5) icon from the application toolbar. The TC references the import part of the data interface of the test script. Multiple test data can be given if required. Test Data and an Alias can be added to Test Data section using Append Row icon. which contains the Target System. transaction SECATT. Under the Configuration tab. Variants can be prepared . Also give the name of Test Script. Variants can be added from Variants tab. The Alias is an alphanumeric name up to three characters.15 And the Last Changed script attribute (Attributes tab -> Extras tab -> Administration Data) will contain only the details of the person who has made changes to script and not to the data.
Manually Creating Variants: In the Test Configuration editor under Variants tab. The left half of the screen displays the variants belonging to a test data container. The Variant Maintenance Assistant window appears. This will insert a new line for variant under ECATTDEFAULT. . To create variants from the Test Data containers. The variant will be copied to Test Configuration side. click on the Append Variant icon. click on the wizard icon (Variant Maintenance Assistant) under the Variants tab. This way multiple variants can be directly added to Variants list. The right half of the screen displays the variants belonging to the test configuration. In the Variants field. Scrolling between the multiple variants of Test Data is available. Under each parameter either give value or leave the field blank. Click on Save (Ctrl+S) button from the standard toolbar. Variants from Test Data Containers: Prerequisite for this option is that Test Data Containers should be maintained under Configuration tab.16 either manually by clicking the icons Append Variant/Insert Variants or from the wizard using test data containers referenced in the Configuration tab. give the name of the variant. Select the variant from the Test Data & click on Attach as variant button.
and variant all refer to a test data container.<variant>) where the parameter name. The value in a field is determined by the following syntax: <parameter name>(<alias>.<variant>) where the parameter name. Choose Insert in column. alias. Click on enter. Select a field belonging to the test configuration. The field will be dynamically linked. The field belonging to the test configuration is filled. Any changes done at TD side will be referred dynamically in TC. Click on Save (Ctrl+S) icon from the standard toolbar. alias. The links will be present for the values of the parameters from TC to TD. Variant will be added to Variants list in TC. All the empty fields in the column are filled. Select an empty field belonging to the test configuration. This way multiple variants can be created. Linking multiple fields in Test Configuration column to a single field of Test Data variant: Select a field belonging to a test data container. And Test Configuration is now ready to execute or to link to TestWorkbench depending on the variant selected. . The value in a field is determined by the following syntax: <parameter name>(<alias>. The value in a field is determined by the following syntax: <parameter name>(<alias>. Linking single field of Test Data variant to Test Configuration variant: Select a field belonging to a test data container. <variant>) where the parameter name. alias. and variant all refer to a test data container. Choose Link individual field.17 Only the parameters in the test data container that match those of the test script are appended. and variant all refer to a test data container. Click on enter. Click on enter.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.