Editing Test Clips

Document created by Chris Sommerstad Employee on Jul 21, 2017Last modified by Jijius Jabez on Aug 11, 2017
Version 2Show Document
  • View in full screen mode

To edit a test clip, go to Central > Test Clips.

Find the test clip you wish to edit and double click its name to open it.

Alternately, right-click the selected test clip and select Open in the context menu.

For long lists, use filtering to locate the test clip. Click the Filter icon on the top right of the Clips list and then apply criteria to narrow the list. When you do so, the Filtering rows appear at the top of the list. Click the drop-down to select criteria and to select from operators for the given field.

Click the Plus (+) button to add criteria, click the Minus (-) button to remove criteria. Click Apply to filter the list by the criteria.

A Test Clip can have one or more of the following clip elements:

    • Message

Messages are the raw text or XML that is sent to a web service or web application, but they occur within the context of the rules and syntax that envelope them. See Message, Playing Messages, and Setting and Using Message Scope.

    • Browser Action

Browser actions are those actions a user performs using a web browser, including keystrokes, mouse actions, text entry, and system actions such as close or submit. See Browser Action.

    • App Action

App actions are those actions a user performs using a mobile app, including tap, swipe, pinch, and many more. See App Action.

    • Database Action

Database actions are those actions that represent a SQL database query in the test. For example, a clip that has the SQL traffic for something like an order placement built in will include numerous SQL statements one query per database action (e.g. clip element). For manual creation of test clips with database actions, users should also specify only one SQL statement (or SQL command) per database action. If multiple SQL statements are bundled for one database action, only one Result for the last SQL statement will be returned and displayed within CloudTest's Result Details widget. Refer to Direct To Database Testing.

    • Collection

Collections are logical containers that organize information in your test clip (and for which metrics are subsequently included in test results). A collection container can represent a web page and its assets (Pages), messages or actions that are sequentially fired (Chains), an ecommerce or similar workflow (Transactions), or a function in which conditional behavior occurs (If-Then-Else and Switch). Refer to Viewing Collections for additional details about collections in the Clip Editor.

    • Script

A script specifies a set of actions to be taken at a specific point in the execution of a Test Composition (via the test clip in which the script has been placed). SOASTA CloudTest Scripts are written in JavaScript. See Script.

    • Delay

A Time Delay is a test clip component that specifies an interval to wait, in milliseconds, before sending the following message or browser action. See Delay.

    • Checkpoint

A checkpoint is a Test Clip component that indicates that no further action take place until a response has been received from the prior message. See Checkpoint and Renaming Checkpoints.

    • Property

SOASTA CloudTest provides three property sets for use in tests. Properties can be defined for test clip components such as messages and browser actions, as well as for test clips, and test compositions. See Property.

Further Steps

See Changing Order of Clip Elements for information about ordering and reordering clip elements in a test clip.

To edit an individual message or browser action, select and double-click it to open its detail in the sub-pane below. For more information, see Editing the Inputs of a Message and Editing a Browser Action Test.

Attachments

    Outcomes