Editing a Test Script on the Test Script Tab Page

On the Test Script tab page, you can compose a test script

of steps (modules) from eCATT or composite (eCATT and third-party test tool steps) test scripts

– or –

of screen components or default components from Component-Based Test Automation test scripts

You define the sequence of the test script steps to be executed and the values of parameters. To concatenate the test script (steps), you define input and output parameters as

empty if the parameter is not used
Fixed, to assign a constant value to a parameter
Local, to pass parameter values within a test script
Exposed, to pass parameter values from one test script to another, or between the parent level and child levels.

This graphic is explained in the accompanying text.

Concatenating Test Scripts or Steps by Defining Local and Exposed Parameters

Note Note

If you use a third-party test tool, the Test Script tab page is not displayed. The content of the test script can only be interpreted by the third-party tool, not by SAP Solution Manager.

If a test case was modified in eCATT, it can no longer be edited in the Test Composition Environment. To edit the test case, choose the Start eCATT pushbutton.

End of the note.

Note Note

Using CBTA

A CBTA test script is made up of child test scripts called components. There are two kinds of components:

Default components are delivered by SAP with the CBTA software. They are stored in the SAP Solution Manager repository for eCATT test scripts. They perform single actions, for example, entering a value in a field, pushing a pushbutton, selecting a tab page.
Screen components are generated after the recording, depending on the screens used in the recorded business scenario. For each screen, which is a logical part of a page, a screen component is generated during the inspection process. This process retrieves static information on the screen from the SUT and generates a screen component. It contains one parameter for each field of the screen. When a value is assigned to such a parameter, the system enters it in the corresponding field, at execution time.
A screen component reflects a single version of a screen. To differentiate between the versions of a screen, the system uses the system data container (SDC) and the target components. The version of a screen is the same on all systems of the same SDC and target component. For other systems, other screen components are created.

You can reuse default and screen components in several test scripts. When a screen is updated, its screen components can be repaired, to make the repair of test scripts easier. This process uses the Technical Bill Of Material (TBOM) and Business Process Change Analysis (BPCA), to reduce the effort of testing after an SUT update. For more information, see

End of the note.

Prerequisites

You have created an eCATT or Component-Based Test Automation test script or a test configuration and maintained the test script attributes. For more information, see

Procedure

Select the Test Script tab page.
To ensure that uploaded test scripts are displayed, choose Refresh.
The test script steps are displayed.

In an eCATT or composite test script, the steps can be test scripts of any test tool type. In a Component-Based Test Automation test script, steps are either default or screen components.

If you use CBTA, you have the following options:
- In the Comment column, you can enter or edit a description of the test script step.
- In the Status column, you can disable a test script step temporarily. During test executions, the step is skipped, so you can, for example, try various variants of a test script without having to remove steps.
To add a test script step, under Test Script Steps do the following:
- For an eCATT or composite test script:
  1. In the Type column, select the type of the test tool with which the test script was created.
  2. In the Name column, select the test script.
  3. Save your entries.
    
    Empty lines are removed automatically.
- For a CBTA test script:
  1. In the Type column, select a default component or a screen component.
    Use default components to perform basic actions, such asentering a value in a field, selecting a tab page, pushing a pushbutton, or clicking on a link.
  2. Use screen components to set the values of a set of fields in one screen (SAP GUI) or views (CRM Web Client or Web Dynpro ABAP).
    To identify the screen or views of a field, do the following:
    
    In CBTA, choose the Get Additional Information pushbutton.
    Select the session showing the field and select (spy) the field with your mouse.
    The technical information is displayed, including the URI that identifies the field, and the screen (program and screen number for SAP GUI) or the application and view (CRM Web Client and Web Dynpro ABAP).
    
    To use this information to create a screen component, choose the Inspection pushbutton.
  3. In the Name column, select the test script.
  4. In the Version column, enter a value (typically 1).
  5. Save your entries, or press Enter to validate your entries, and save later.
  Empty lines are removed automatically.
Under Test Script Steps, use the Up/Down pushbuttons to define the sequence of the test script steps.
If you have performed a step twice during the recording by mistake, to remove the incorrect test script step, choose Remove.
To configure a selected test script step, you have the following options:
- To define the values passed to the script steps of a sequence (import and export parameters), on the Parameters sub tab page below, you can do the following:
  1. In the Usage field, define the usage type:
    
    No value: No parameter value is passed to the parameter of the test script. The test script parameter does not have a default value.
    Fixed: A constant value is passed to the parameter. The constant value does not depend on the execution of the script.
    
    Example
    You always want to create a sales order for 5 pumps. For the parameter “Quantity”, in the Value column, you enter 5.
    
    If you set usage to Fixed but do not specify a value, the value NULL is used in the test script.
    
    To define an empty string value, use the value %BLANK%.
    
    End of the example.
    
    Exposed: The parameter is mapped to the parameter of the parent script. The parameter value is passed from (import parameters) or passed to (export parameters) the parameter of the parent script.
    Import parameters can receive the values from the test data container.
    
    Several exposed import parameters can receive their values from the same parent script parameter.
    
    A single exposed export parameter can pass its value to several export parameters of the parent script.
    
    Example
    You want to create a main test script comprising 3 steps (scripts) with the following parameters:
    
    Create quotation
    Import parameters: Customer, Material, Quantity
    
    Export parameter: Quotation Number.
    
    Create sales order from quotation
    
    Import parameter: Quotation Number
    
    Export parameter: Sales Order Number
    
    Create delivery from sales order
    
    Import parameter: Sales Order Number
    
    Export parameter: Delivery Number
    
    You put 3 of the steps in the sequence. To be able to execute the main script for a different customer, material and quantity, you have to know the delivery number created at the end. To do so, set the usage type to Exposed for the following parameters:
    
    Import parameters Customer, Material, Quantity of the script “Create quotation”
    Export parameter Delivery Number of the test script “Create delivery from sales order”
    
    End of the example.
    
    Local: The value passed to the parameter is mapped into the parameter of another step. The value actually used during the execution of the test script depends on the execution of the parent script and the values created in the preceding steps.
    
    Example
    You want to pass the value of parameter Quotation Number created by the “Create Quotation” test script step to the “Create sales order from quotation” test script step. To do so, set the usage type to Local and map these 2 parameters between them. To do so, in the Reference Parameter column, assign the name of one parameter to the other.
    
    End of the example.
  2. Enter data as required.
    
    Component-Based Test Automatin uses Unified Resource Identifiers (URIs) to identify controls on the tested page. To retrieve a URI, choose the Get Additional Information pushbutton. For more information, see the Component-Based Test Automation Default Component Guide on SAP Service Marketplace at http://service.sap.com/support Overview Processes Media Library Test Management .
- To display SAP attributes of an eCATT test script or of a test script created with a third-party test tool, choose the Attributes sub tab page.
  To change the attributes, under Test Script Steps, in the Name column, select the test script. For more information, see Maintaining SAP Attributes on the Attributes Tab Page.
- To display the description, if available, choose the Description sub tab page.
  
  For test scripts created with a third-party test tool, to select either the SAP description or the third-party test tool description, select the respective radio button.
- To display the screen output of a test script, if available, choose the Image tab page.
- To check where a test script is used, select the test script and choose Where-Used. Test Script .
- To edit or display a test script step in a new session, in the Name column, choose the test script.
  If the third-party tool in which the script was created is not available, you go to the eCATT wrapper test script.
If a test execution fails, you can maintain the parameter values and update the set of parameters of a screen component (only for test scripts recorded with Component-Based Test Automation).

Do the following:
1. Select the screen component.
2. Choose CBTA Inspection.
  You go to the Inspection Wizard screen.
3. Select the SAP GUI screen or the CRM web client or Web Dynpro ABAP view.
4. To create the screen components, start the inspection process.
5. In Test Composition Environment, select the new screen component.
6. On the Parameter sub tab page, change the parameter values, where necessary.