Collections and Collection Types
Collections are logical containers that organize information in the test clip (and for which metrics are subsequently included in test results).
A container can represent a web page (Pages), messages or actions that are sequentially organized in a way that mimics network behavior (Chains), user-organized messages or actions (Groups), a representation of a programmatic workflow (Transactions), or a function in which conditional behavior occurs (If-Then-Else and Switch).
Within the Clip Editor and in Result Details, each collection type is indicated by a distinct icon and expands/collapses similarly. Each collection object has its own scope as indicated by the lock icon on the lower right. Click the Plus (+) sign to expand a collection and Minus (-) to collapse it.
Collections in the Clip Editor
The Clip Editor shows collections collapsed by default. Expand a collection by clicking its Plus (+) icon.
Once expanded, a collection in Icon view occupies an entire row in the Clip Editor workspace with following elements resuming in the next row.
For example, in the test clip to the right, the login (1) page was the item in the fourth position on the first row, however, once expanded it occupies the second row as shown below. All the individual resources prior to this page still occupy the first row.
The Clip Editor supports all collection types: Pages, Groups, Chains, Transactions, If-Then-Else, and Switch. Using these collection types, CloudTest performs important browser simulation tasks.
Within the Clip Editor, each collection type is indicated by a distinct icon and expands/collapses similarly. Each collection object has its own scope as indicated by the lock icon on the lower right. Click the Plus (+) sign to expand a collection and Minus (-) to collapse it.
Pages can either be automatically created (using the Create a Clip from Recording Wizard) or manually created from within the Clip Editor. Both chains and groups are manually created.
Chains are user-specified groups of clip elements that behave as one unit and always play sequentially. Chains can include delays, messages, scripts and browser actions. This icon shows a chain linking two Content-Types.
Groups are user-specified groups of clip elements that behave as one unit but have no additional properties such as timing (they have the same timing as their containing Clip). Groups can include any item that is permitted in the containing Clip. This icon shows a cascade of content types in a single row.
Pages model, or simulate, the way real world web pages behave. They have a top-level HTML page, which has resources, sometimes referred to in the load-testing world as “assets”. This icon shows an HTML Document and its additional resources.
- Pages are used to gather all of the requests for a given web page or node into one container so that they can easily be understood as a “page” during testing.
- Pages include special timing and can be automatically created from recordings, or manually by user-selection. Once created, pages behave as one unit with a defined “HTML Document”.
The screenshot on the right shows the Clip Editor in Icon view with an expanded page called wikipedia. The background for all "collections" is now dark blue. For pages, resources can be turned checked on or off, whether they are static or dynamic.
For example, CloudTest plays the first message (this is called the HTML Document), and when its response is returned all subsequent messages in the Page are played in a way that simulates browser behavior (e.g. in a “burst”-like manner, using the number of connections per host as specified in the Target).
- When static resources are used, CloudTest plays exactly those resources that are specified in the page, regardless of whether they were recorded or inserted during clip editing.
- When dynamic resources are used, CloudTest parses the response of the HTML Document and dynamically makes requests for all of the resources found in that response.
Dynamic simulates what browsers do, and is a more robust way to handle pages since the resources in the HTML Document may change. For example, using static pages will not submit the right requests to the servers if an HTML Document has changed since it was recorded, but using dynamic pages will.
A Page can use static resources, dynamic resources, or both simultaneously.
Pages contain two “segments”. The first segment contains the HTML document as well as optionally scripts and delays. The items in the first segment play sequentially. The second segment contains static resource Messages, which are played in a “burst”.
In an expanded Page, the parent HTML page request (e.g. HTML Document) is shown to the left of the vertical bar. On the right of the bar, the static resources that the page uses are shown. If the clip was created from a recording, then its static resources are those that existed at that time.
As with chains in prior releases, items within collections can be reordered, added and subtracted using delete as well as clipboard operations. The addition of some elements is subject to restriction by collection type and clip element type.
Uncheck static to dynamically retrieve this page’s resources dynamically instead.
Note: Whenever a page is set to “dynamically” retrieve resources, the CSS resources included in the main HTML Document will also be retrieved. Pages will dynamically process the referred URLs and CSS files in any CSS file referred to by the main HTML Document of a page. To turn off the retrieval of CSS resources (beyond the first level), check the "Do not retrieve CSS resources" checkbox at the appropriate level.
Uncheck all resources to disable the page in all tests. This remains in effect until the resources are re-checked.
When collections contain more items than can be displayed, the collection scrollbar will appear in both icon and list views. While being dragged, the scrollbar displays the numerical range of items in view of the total number (e.g. 20-34 of 65 as shown below.
For collections in list view the scrollbar appears on the left and displays the range vertically.