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 image shows an HTML Document and its additional resources.
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).
|Static Resources in Pages|
Resource which are set to static retrival are diaplayed in the cloudtest UI as shown in image
|Dynamic Resources in Pages|
Resource which are set to dynami retrival are grayed out in the cloudtest UI as shown in image
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”.
|Viewing Expanded Collections|
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 resources in all tests. This remains in effect until the resources are re-checked.