To open an existing test composition in the Composition Editor, click Central list > Test Compositions. Find the test composition that you want to open and double-click its name in the list.
For long lists, use filtering to locate the test composition. 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.
The Composition Editor appears in a new tab with the given test composition in display.
There are a number of main task areas to consider when building test complexity in the Composition Editor:
- The type of timing (timing must be set prior to adding test clips). The default timing type is sequenced. Refer to Adjusting Band Timing and Adjusting Clip Timing.
- The test clips to add. Refer to Adding Test Clips to Test Compositions.
- The number of repeats on a track (virtual users). Refer to Setting Repeats on Tracks and Test Clips.
- The number and type of repeats on a test clip. Refer to Setting Repeats on Tracks and Test Clips.
- The number of tracks and the location where they will be played. Refer to Specifying Maestro Locations.
- The system and custom properties to set for the test composition and its components. Refer to Test Clip/Target-level System/Custom Properties.
- The play mode to set (General, Load, or Custom settings). Refer to Play Mode and Results Logging.
- The time interval (for test compositions with timed bands). Refer to Adjusting Band Timing or Adjusting Clip Timing.
Additionally, the use of the Repeat Composition button (to play a test composition in a loop until stopped) and Play Options such as Preview mode should be considered.
Setting Scopes in Test Compositions
SOASTA CloudTest provides the ability to set scope on the surface of objects in the repository, including bands, tracks, test clips, as well as for all clip elements (messages, browser actions, delays, checkpoints, scripts, and chains).
Setting scope defines whether an item is private, public, or local. An item's scope determines whether information about an item can be accessed from outside of that item. What information that may be depends upon the item itself.
- Private means the item’s information cannot be accessed from the outside
- Local means that an item’s information can be accessed only by other items within the same parent container
For example, making a Message local means that the Message can only be accessed by other items within the same Clip
- Public means the item’s information can be accessed from anywhere.
Scope can be set for a selected object by applying Public, Private, or Local from the Etc. drop-down menu.
For example, for a message the information at stake in scope includes the request to be sent and the response received. For a target, scope includes System Properties such as the URL. For a Delay it includes the System Property that specifies the length of the Delay.