Show TOC

Procedure documentationComposing Modular Test Scripts on the Test Script Tab Page Locate this document in the navigation structure

 

On the Test Script tab page, you can compose an eCATT or Component-Based Test Automation test script, manually. You define the sequence of the test script steps to be executed and then, define the values for parameters of the test script (steps).

Note Note

If you use a third-party test tool, the Test Script tab page is not displayed because SAP Solution Manager cannot interpret the internal structure of the test script.

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.

Prerequisites

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

Procedure

  1. To ensure that uploaded test scripts are displayed, choose Refresh.

    The screen and default components on which the test script steps are executed, are displayed.

    Note Note

    The names of the table fields of a CRM Web UI table control cannot be retrieved. A placeholder default component TAO_CRM_C_F_SETVALUE, is displayed.

    End of the note.

  2. To add a test script step, under Test Script Steps do the following:

    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.

  3. Under Test Script Steps, use the Up/Down pushbuttons to define the sequence of the test script steps.

  4. If you have made performed a step twice during the recording by mistake, to remove the incorrect test script step, choose Remove.

  5. 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, 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 default value is passed to the parameter. The default value does not depend on the execution of the script.

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

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

    • 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 and Tool-specific 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.

      SAP descriptions can be edited in eCATT.

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

  6. If a test execution fails, you can update parameter values, where necessary, and maintain the test script (only for test scripts recorded with Component-Based Test Automation).

    To do so, do the following:

    1. Select the screen component.

    2. Choose CBTA Inspection.

      You go to the Inspection Wizard screen.

    3. On the Parameter sub tab page, change the parameter values, where necessary.