UI (page vs. resource sections)

Document created by Dave Murphy Employee on Jul 19, 2017
Version 1Show Document
  • View in full screen mode

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.

  • 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 simulate web browser behavior. They include a main HTML Document, and all of the resources (JavaScript, CSS, images, etc.) that it includes. Pages include special timing, while groups include no such timing. On playback, the first message in a page is played first and then the subsequent messages in the Page—both static and dynamic—are played in bursts similar to a burst of file requests made from a web browser

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
  • 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. 

       Resource which are set to static retrival are diaplayed in the cloudtest UI as shown in image    

Dynamic Resources in Pages
  • 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.

       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.

However, CloudTest cannot always determine with complete accuracy what resources a browser might retrieve.  For example, if there is dynamic JavaScript that executes in the page, that would not be detected by CloudTest as it does not actually execute any received JavaScript files.  Static Resources can be added to the Page to manually cause such resources to be retrieved.

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.