Show TOC

Procedure documentationFinishing the Creation of a Test Configuration or a Test Script Locate this document in the navigation structure

 

You can, for example, define search terms, to find the test script later, or assign test data variants.

Prerequisites

You have defined the parameters of the test script.

Procedure

  1. Optional (for test configurations only): To reuse a test, but change the values that the test uses, add references to one or more test data containers.

    For more information, see Test Configuration Editor.

    1. On the Test Data tab page, choose Add.

    2. In the Alias column, enter an alias.

      When parameters of the script are mapped onto the parameters of a test data container, the references are displayed. If the name of a test data container is too long it can be difficult to recognize the references. To monitor the mapping, enter an alphanumeric name of up to three characters for the test data container.

    3. In the Test Data Container column, select the test data container.

      In the Title field, the name of the test data container is displayed.

      If the test data container contains external test data variants, the corresponding checkbox is selected, and the name of the file containing the external test data variants, is displayed.

    4. Save your entries.

      The test data container is assigned to your test configuration.

    5. To create test data variants for a test configuration, you have the following option:

      • You can choose whether to display the value of a parameter or the test data container alias and the number of the variant from which the parameter value is taken.

        • To display the value of the parameter, choose Value. 200, for example, is displayed.

        • To display the test data container alias and parameter name, choose Reference:

          Example Example

          If you have a test data container with the alias TD1, instead of the value 200 you could see <parameter name>(<test data container alias>,<number of the test data container variant>), for example I_ORDER_TYPE(TD1,1).

          End of the example.

      • To assign a test data variant to the parameters of your test configuration, do the following:

        1. Choose the Test Data Assignment Wizard pushbutton. The pushbutton is only active if the test script has parameters.

          The Variant Maintenance Wizard starts.

        2. .Enter data as required.

        3. Choose Transfer Wizard Result to Configuration.

        4. On the Test Data tab page, choose Refresh.

          A dialog box appears.

        5. To confirm, choose Yes.

          Under Test Data Variants, the test data variant is displayed.

        6. To allow the test data variant to be selected for execution, select the Execute checkbox.

          If you select multiple test data variants, you can specify the one to be executed, in the Start Options screen, when executing the test case.

        7. Save your entries.

  2. Optional: To use advanced eCATT functions to edit the test configuration, choose   Goto   Expert Mode  .

  3. Save your entries.

  4. Optional: To replace the test script automatically assigned to the test configuration, you have the following options:

    • To assign a copy of an existing test script which you plan to change, choose   Assign Script   Copy Existing  .

    • To create a reference to an existing test script, choose   Assign Script   Existing  .

    • To create a new test script, choose   Assign Script   New  .

  5. Optional: If you use Component-Based Test Automation, you can edit the test script parameters. For more information, see Defining the Test Script Interface on the Parameters Tab Page.

  6. To find the test script later, you can enter search terms. For more information, see Defining Search Terms on the Search Terms Tab Page.

  7. Save your entries.

  8. Optional: To use advanced functions to edit the test script, choose   Goto   Expert mode   (transaction SECATT).

    Note Note

    If you edit a test configuration or test script with transaction SECATT, you cannot edit it again later in the test composition environment.

    End of the note.