Collection Details

Collections are logical containers that organize information in your test clip (and for which metrics are subsequently included in test results). A collection container can represent a web page and its assets (Pages), messages or actions that are sequentially fired (Chains), an ecommerce or similar workflow (Transactions), or a function in which conditional behavior occurs (If-Then-Else and Switch). Refer to Viewing Collections for additional details about collections in the Clip Editor.

  • Band Name – The band in which this test clip was executed. See Change Band Timing Type.
  • Band Index – The index of the band in the test composition.
  • Track Name – The name of the track in the test composition.
  • Track Index – The index of the track in the test composition.
  • Clip Name – The name of the test clip in the test composition.
  • Clip Index – The index of the test clip in the composition.
  • Chain Name – The name of the chain.
  • Chain Index – The index of the chain in the test clip.
  • Error – The error text (or NONE if there was no error).
  • Type – The chain type.
  • Completion Status – The completion status. For example, Playing or Completed.
  • Message Response Count – The number of message responses received.
  • Total Msg. Response Time –The total response time for all HTTP messages within the collection including those that are contained in other collections and clips which are nested at any level within this collection.
  • Min. Msg. Response Time –The minimum message response time for the same set of messages listed above.
  • Bytes Sent –The sum of bytes sent for all responses to actions within the collection and within any nested collections.
  • Bytes Received –The total number of bytes received from the remote server for actions within the collection and within any nested collections, including the status line, the headers, the body, and all separating whitespace. If the response requires any post-processing (e.g. decompression or binary-to-text-conversion), this will be the number of bytes *before* the post-processing took place.
  • Duration –The period of time, in milliseconds, between when the collection started and when it completed. This is a wall clock duration and includes any system overhead as well as delays.
  • Start Time – The time the chain was fired
  • Message Count – The count of messages in the clip.
  • BrowserAction Count – The count of browser actions in the clip.
  • Script Count – The count of scripts in the clip.
  • Checkpoint Count – The count of checkpoints in the clip.
  • Delay Count – The count of time delays in the clip. Refer to Time Delay.
  • Effective Duration – The length of time, in milliseconds (ms), for the collection to start until it completed. This is not the time for the elements within the container. In the context of a collections this will be the period of time, in milliseconds, between when the first operation (HTTP message, browser action, database action, etc) or delay in the collection started and when the last operation completed. System overhead time is not included.