- Subscribe to RSS Feed
- Bookmark
- Subscribe
- Email to a Friend
- Printer Friendly Page
- Report Inappropriate Content
Running a Test (Player Controls, Playlists and Compositio ns)
Player ControlThe CloudTest Player Control present in both the Composition Editor and the Player Status > Compositions screen in Central use the same simple play/pause/stop buttons familiar to users of modern video equipment. This control includes a Play, a Pause, and a Stop button. |
|
Status Log IndicatorThe Status Indicator (upper right) reports about the status of played compositions. This indicator uses a single spinner, with drop-down details. This button is active in the Composition Editor and Recording editors. When a test composition is played, loaded, unloaded, previewed, closing, stopped, or completes, the Status Indicator provides visual confirmation. |
|
|
Pop-up status about active recordings, loading and unloading compositions, and passed or failed test composition is posted and drop-down links are presented when error messages occur. |
|
Play Modes and WarningsIn order to facilitate fast play for larger test compositions, CloudTest utilizes load/unload as well as play modes. For that reason, in some cases warnings are posted for the user to confirm certain actions. Attempting to unload a test composition that is already playing will result in the prompt shown on the right. |
|
|
In addition to warnings about unloading a playing composition, attempting play a composition with >= 10 Virtual Users will also result in a warning. CloudTest uses play modes to guide the use of virtual users in test compositions. Large tests with more than 10 virtual users should use Load mode. See Play Mode and Results Logging for more information about play modes in CloudTest. |
|
|
Clicking the Stop button (either in the Composition Editor toolbar or from the Central list > Player Status display) displays the Stop dialog box and a choice between Stop and Force Stop (as shown on the right). Refer to Stopping a Composition for more information. |
|
Play or Pause a Test Compostion in Composition EditorClick the Play button to play a test composition. If the test has already been loaded (using the Loading/Unloading button), the composition plays immediately. Click the Pause button on the Player Control to pause a playing test. All message sends will be paused until resumed. Responses to previously sent messages are still received. While a test is paused, the Result Details dashboard displays the Paused icon (instead of the Spinner icon that displays during play). |
|
|
The Status Log indicator on the top right of the Composition Editor also indicates the paused status of play. Status updates appear to indicate the status of a playing composition. |
|
While the test plays, the Result Details dashboard displays the Spinner icon. |
|
Pause a Test Composition via Player Status – CompositionsThe Central > Player Status > Compositions page now includes a Pause button in the player control as well.
|
|
|
When a composition is paused, the Player Status – Compositions log also indicates that state. |
|
|
A playlist is a list of Test Compositions that can be played either sequentially or simultaneously. Playlists serve the same purpose as playlists in digital music applications. The Playlists can be found at the bottom of the Central list. You can add one or more compositions to the playlist. The playlist, like any other object in SOASTA CloudTest can be called from a script. When a playlist is selected, click the Play button on the toolbar to play all of its contents. The playlist fires in the order of the items listed within it. The runtime progress of the playlist can be checked in the Central > Player status. As with completed results, the test is evaluated in terms of success or failure. |
![]() |
Create a New Playlist
|
![]() |
|
![]() |
If the playlist is not visible after doing so, click the arrow next to the Playlists icon until the playlist appears. |
![]() |
|
![]() |
|
|
The playlist fires in the order of the items listed within it. As with completed results, the test is evaluated in terms of success or failure in the Player Status list. |
![]() |















