Previous Topic: Add a Test StepNext Topic: Configure Test Steps


Add a Test Step - Example

This example adds a step to the multi-tier-combo test case in the examples directory. A new Dynamic Java Execution step will be added to the multi-tier-combo test case, after the Get User step.

Follow these steps:

  1. Click the Add Step button.

    A panel that lists the common test steps opens.

    Multi-tier-combo test case, Steps in model menu

  2. Select the main category of the step to be configured (for example, Web/Web Services, Java/J2EE, and Utilities).

    The sub category opens.

  3. To add a step to the test case, click the step.

    The step editor for the selected test case opens. Each step type has a different step editor.

  4. To add a Dynamic Java Execution step after the Get User step, right-click the Get User step and select the Dynamic Java Execution step.

    The step is added and the step editor for the Dynamic Java Execution step opens.

    Step editor for the Dynamic Java Execution step

Add Step Information

Follow these steps:

  1. To add the basic step information, open and expand the Step Information tab in the Elements tree in the right panel.

    The Step Information editor opens.

    Step Information editor

  2. Enter the following parameters:
    Name

    The name of the step. You can rename the step in this text box.

    Think Time

    The amount of time the test case waits before executing this step. Think time lets DevTest simulate the amount of time it takes a user to decide what to do before taking action. To specify how the time is calculated:

    1. Select the time unit by clicking the appropriate drop-down (millis, seconds, minutes)
    2. Enter a starting value in the Think Time field
    3. In the To field, enter an end value and a time indicator.

      DevTest picks a random think time in the specified range. For example, to simulate a user think time for a random interval between 500 milliseconds and 1 second, enter "500 millis" and "1 seconds."

    Use Global Filters

    To instruct the step to use global filters, select this box. For more information about filters, see Add a Filter in Using CA Application Test.

    Quiet

    Select this box if you want DevTest to ignore this step for response time events, and performance calculations.

    Execute On

    Specifies the simulator that the step runs on. Specify specific simulators for steps that must run on a specific computer. For example, when reading a log file, run the step on the computer where the log resides.

    Next

    The next step to execute in the test. If the step ends the test case execution, you will not specify a next step. An assertion that fires in this step overrides this value.