Exporting Results

Document created by Chris Sommerstad Employee on Jul 22, 2017Last modified by Dave Murphy on Sep 28, 2017
Version 4Show Document
  • View in full screen mode

Result objects can be exported into a variety of formats:  SOASTA XML Definition, Comma Separated Value (CSV), XML Spreadsheet (which can be read by Excel) as well as RSS 2.0 files. Individual, or in some cases, multiple results can be selected and exported for the given metric by selecting one of these formats; results can be selected from either the Compositions list or from the Results list in Central.

Multiple result exports are supported for tests run in parallel for the following selections: Page Completions, Page Average Durations, Transaction Completions, Transaction Average Durations, and Fundamentals Summary.

For a separate overview and metric definitions, refer to Understanding Metrics in CloudTest Analytics.

Additionally, users should make themselves aware of CloudTest Objects to which metrics are applied, including Bands, Tracks, various Clip Elements such as Collections, Test Clips, and Test Compositions.

Export Charts to Excel

Widgets listed under Widget Types can be exported to Microsoft Excel in CSV format using the Export to Excel (CSV) icon.

To export a chart, place the mouse cursor or the right corner of the chart’s menu bar.

The file is opened by the browser download mechanism and the file to export takes the form of “<Widget name> export.csv”.

The format of the exported comma-separate-value file depends on the type of widget that is exported. A single chart will have a column for each of its axes.

The same chart that has been split by a dimension will have a column for each split dimension (e.g. one column for each location/domain/clip).

For an analysis widget, the CSV file will have a column for each of the columns within the widget. For each node in the tree an additional column appears (e.g. Composition > Clip > Collection, etc.).

Export One or More Results from the Results List

  1. In Central, find the existing result(s) either under Results or by clicking the arrow key next to expand a composition in the Compositions list to make a multiple selection.

To select a range, hold down the SHIFT key and select the second item.


  1. Click the Export button on the toolbar (alternately, right-click and choose Export from the context menu). The Export dialog box appears.

  1. Next, choose an export format.

When you choose CSV, XML Spreadsheet, or RSS, then another drop down will display for Data Source selection.

In the example on the right, the CSV option is selected, with the available data sources appearing in the drop-down.

The Data Source list will contain the following choices:

Note: Exported results are not available for the export format, XML Definition.

  1. Press the OK button. The standard Browser download dialog will display.

Export Result Tables

For the selections in the Data Source drop-down list above, the following fields are exported:

Clip Element Details

This export contains information for each clip element executed during the test. It contains one row for each message or script or other element executed during the test. This information is only available if the test was run with “Save Clip Element Details” turned on.

  • Band Name – The band in which this test clip was executed.
  • 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. If the track does not repeat then this field is blank.
  • Clip Name – The name of the test clip in the test composition.
  • Container Index – The index of the container indicating the repeat of the container or blank if the container did not repeat.
  • Clip Element Name – The name of the clip element.
  • Clip Element Index – The index of the chain in the test clip.
  • Clip Element Name – The name of the clip element in the test clip. For example, Message1.
  • Clip Element Index – The index of the given clip element indicating the repeat of the clip element or blank if the clip element did not repeat.
  • Clip Element Type – The type of clip element, such as message, browser action, app action, delay, checkpoint, or collection.
  • Target Name – The underlying target name for the given clip element.
  • Operation – The type of operation that was executed. For example, a GET in HTML or an operation in a SOAP-based WSDL.
  • Server – The name of the test server that ran this clip element.
  • Location – The location that was defined for the given test server. Refer to Specifying Maestro Locations and Play Options.
  • Start (Offset) – The time the clip element was fired as an offset from the start of the test.
  • Start (Absolute) – The date/time the clip element was fired.
  • Send Time – The time the clip element was sent.
  • Receive Time – The time the clip element was received.
  • TTFB - The time to first byte for the clip element. TTFB is the amount of time from the start of the request to the first byte being received from the server. TTFB includes the following: establishing the HTTP connection, sending the request to the remote server, and waiting for the first response byte.
  • TTLB - The time to last bye for the clip element. The amount of time from the start of the request to the last byte being received from the server. TTLB includes the following: establishing the HTTP connection, sending the request to the remote server, and receiving the complete response. Does not include response "processing" (e.g. de-compressing, etc.).For example, 423409.
  • DNS Lookup Time - The total time for DNS Lookup to complete for this clip element.
  • Offset in Container - The (start) offset time for the given clip element from its parent container.
  • Wait for Connection Pool Time – The wait time in the connection pool.
  • Delta From Scheduled Time –The difference in a timed container between the offset of the actual start time from the scheduled time, in milliseconds (ms).
  • Delta Scheduled Duration – The difference in a timed container between the scheduled duration from send to receive and the actual one.
  • Validation Error – The number of validation errors.
  • Bytes Sent – The total number of bytes for the given clip element sent to the remote server, including the request line, the headers, the body, and all separating whitespace.
  • Bytes Received –The total number of bytes received for the given clip element from the remote server, 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.

Event Details

This export lists event detail information that corresponds to the same info found in the Result Details, Events List for the given result.

  • Type – The event type (e.g. Composition).
  • Server – The server by its CloudTest repository name. Refer to Specifying Maestro Locations and Play Options.
  • Event Time (Offset) – The event time as an offset from the start of the test.
  • Event Time (Absolute)– The calendar date/time of the event. For example, 2012-01-20 15:06:31 PST.
  • Event Number – The event number as it occurs in the sequence of the test composition (a series beginning with 1).
  • Level – The numeric event level. The possible values are 100 (equals None) 200 (equals Error), 300 (equals Statistics), 400 (equals Info), and 500 (equals Verbose).
  • Code – Same as the Event Code column in the Result Details, Events list. Possible values include: start (Composition Start), machinf (Server Info), streq (Stop Request), stats (Statistics), exstats (Statistics about an object's activity over time), stop (Composition Stop, etc.). Refer to the Result Details, Events List, Description column for an explanation of any event code you have received.
  • Text – Same as the Result Details, Events List, Description column. Generally,elaborates upon the Code column's fuller context.
  • Details1 – The same as the Result Details, Events List, Details1 column for an explanation of any event code you have received. Any additional information is posted to the Result Details, Events List, Details2 column. For example server information that corresponds to a Server Info (machinf) event:

    OS: MacOSX (Mac OS X 10.6.8, 10K549)
    Memory: 34359738368 bytes
    CPU's:
    1. Intel(R) Xeon(R) CPU E5620 @ 2.40GHz (2400 MHz)
    2. Intel(R) Xeon(R) CPU E5620 @ 2.40GHz (2400 MHz)

Time Aggregate

This export contains aggregated information for each second of the test. There is one row for each second. The fields are:

  • Start Second – The second offset into the test using a ‘round up’ method. For example a message sent at 3.454 of the test will be included in the Start Second of ‘4’.
  • Message and BrowserActions Count – Number of messages plus browser actions processed in this second.
  • Send Count – The number of messages successfully sent during this second.
  • Receive Count – The number of messages received during this second
  • Total Response Time – The sum of the response times for every message sent during the second. Only messages which are successfully sent are included.
  • Avg. Response Time – The Average Response Time per second, which is calculated as Total Response Time divided by Send Count.
  • Min. Response Time – The least response time sent during the second. Only messages that are successfully sent are included.
  • Max. Response Time - The largest response time sent during the second. Only messages that are successfully sent are included.
  • Total Time - The sum of the Total Tmes for every message attempted to send during the second. Total Time is the amount of time spent sending a Message and receiving the response, including "Send Time", "Receive Time" and any necessary retries. Messages that did not receive a response due to connection timeouts or other errors, will still have a total time. For Non-Messages, the Total Time is the time to complete the action. Delays, Browser Actions, App Actions, and Database Actions will have a total time.
  • Min. Total Time - The least Total Time spent sending a Message and receiving the response during the second. Timeouts and other times are included.
  • Max. Total Time - The largest Total Time spent sending a Message the response during the second. This field presents the highest of the Total Times for every message attempted to send during the second. Timeouts and other times are included.
  • TTFB - The time to first byte for the clip element. TTFB is the amount of time from the start of the request to the first byte being received from the server. TTFB includes the following: establishing the HTTP connection, sending the request to the remote server, and waiting for the first response byte.
  • TTLB - The time to last bye for the clip element. TTLB is the amount of time from the start of the request to the last byte being received from the server. Includes the following: establishing the HTTP connection, sending the request to the remote server, and receiving the complete response. Does notinclude response "processing" (e.g. de-compressing, etc.).
  • DNS Lookup Time - The amount of time spent resolving the host name using DNS.
  • Offset in Container - The (start) offset time for the given clip element from the start time of its parent container.
  • Wait for Connection Pool Time- The time spent waiting in connection pool(s) for this clip element.
  • Delta From Scheduled Time - The difference in a timed container between the offset of the actual start time from the scheduled time, in milliseconds (ms).
  • Delta Scheduled Duration - The difference in a timed container between the scheduled duration and actual duration for this clip element.
  • Validation Error - The number of validation errors for the clip element. Validations are the technique used to verify that a test event occurs as expected. For example, verifying expected text on a web site landing page after login, or expected text in a WebUI or mobile app after a view is loaded.
  • Bytes Sent – The per second total number of bytes sent to the remote server, including the request line, the headers, the body, and all separating whitespace.
  • Bytes Received – The per second total number of bytes received from the remote server, 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.

Clip Element Aggregate

This export contains aggregated information for every clip element in the test. There is one row for each clip element and error combination.

  • Container Name – The name of the container for the given clip element (e.g. test clip, nested clip, or collection of type) in the test composition.
  • Clip Element Name – The name of the clip element in the test clip. For example, Message1.
  • Error – Displays the error text (or NONE if the clip element had no error).
  • URL Protocol – The type of URL protocol in use, usually "HTTP".
  • URL Domain – The originating domain of the clip element's URL.
  • URL Path – The clip element's path on the given server, starting from the URL's root ("/").
  • Clip Element Type – The type of clip element, such as message, browser action, databse action, delay, checkpoint, or collection (by type).
  • Count – The count of clip elements. For example, eight for a message with eight repeats.
  • Send Count – The send count for the clip element. For example, eight messages sent.
  • Total Response Time – The sum of all of the clip element’s duration values for all actions in this container and containers it contains that did complete a request (see the collection's Response Count). Note that actions can execute in parallel, especially in Pages, so this sum can be longer than the duration of the container itself.
  • Avg. Response Time – The average response time for the clip element. For example, 439.
  • Min Response Time – The minimum response time. For example, 199.
  • Max Response Time – The maximum response time. For example, 873
  • Total Time – The total time for the clip element, including send and receive. For example 3519.
  • Min. Total Time – The minimum total time. For example, 199.
  • Max. Total Time – The maximum total time. For example, 873.
  • Avg. TTFB - The average time to first byte for the URL. TTFB is the amount of time from the start of the request to the first byte being received from the server. TTFB includes the following: establishing the HTTP connection, sending the request to the remote server, and waiting for the first response byte.
  • Avg. TTLB-TTFB - The average time to last byte minus the time to first byte for the URL.
  • Total Offset - The total of the (start time) offsets into the immediate parent of the clip element such as a page.
  • Avg. Offset in Container - The average (start) offset time for the given clip element from its parent container.
  • Total DNS Lookup Time - The sum total of time for DNS Lookup to complete for this clip element (e.g. when repeats are in use).
  • Avg. DNS Lookup Time - The avg. time for DNS Lookup to complete for this clip element (e.g. when repeats are in use).
  • Total Connection Establish Time - The total time taken to establlsh an HTTP(s) connection(s) for this clip element.
  • Avg. Connection Establish Time - The average time taken per repeat to establlsh an HTTP(s) connection(s) for this clip element.
  • Total Wait for Connection Pool Time - The total time spent waiting in connection pool(s) for this clip element.
  • Avg. Wait for Connection Pool Time - The average time spent waiting in connection pool(s) for this clip element per repeat.
  • Total Send Time – The total time to send each clip element successfully for all repeats. This includes sending the request content to the server (including request line, headers, and body). The does not include any of the following: establishing the HTTP connection, waiting for the server to respond, or processing the server response.
  • Avg Send Time – The average time to send each clip element per repeat. This includes sending the request content to the server (including request line, headers, and body). The does not include any of the following: establishing the HTTP connection, waiting for the server to respond, or processing the server response.
  • Bytes Sent – The total number of bytes sent for the given clip element successfully sent during the second.
  • Bytes Received – The total number of bytes received from the remote server during the second, 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.
  • Total Errors – The Total number of messages with errors for messages attempted to send during the second.
  • Validation Errors - The number of validation errors for the clip element. Validations are the technique used to verify that a test event occurs as expected. For example, verifying expected text on a web site landing page after login, or expected text in a WebUI or mobile app after a view is loaded.

Clip Details

This export contains information for each clip executed during the test. It contains one row for each clip instance. This information is only available if the test was run with "Save Clip Element Details" turned on in the composition's results logging properties. See Results Logging and Play Modes.

  • 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. For example, in a test composition with three clips, 0, 1, or 2.
  • Error – The error text (or NONE if no error).
  • Type – The type of test clip. For example, a MessageClip.
  • Completion Status – The completion status. For example, Playing or Completed.
  • Message Response Count – The number of message responses received.
  • Total Message Response Time – The sum of response times.
  • Min. Msg. Response Time – The minimum time a response took to be received.
  • Max. Msg. Response Time – The maximum time a response took to be received.
  • Bytes Sent – The sum of the total number of bytes sent to the remote server, including the request line, the headers, the body, and all separating whitespace.
  • Bytes Received – The total number of bytes received from the remote server for the given clip during the second, 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 duration of play for the test clip.
  • Start Time – The time at which the clip 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 test clip to start until it completed. This is not the time for the elements within the container.

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.

Clip Aggregate

This export contains aggregated information for each clip executed during the test. It contains one row for each clip/error/completion status/Start Time combination regardless of how many times that clip was executed during the second or from which track or band it was executed.

  • Clip Name – The name of the test clip in the test composition.
  • Error – The error text (or NONE if no error).
  • Completion Status – The completion status. For example, Playing or Completed.
  • Start Second – The second when the given clip started.
  • Count – The count for the clip aggregate.
  • Total Duration – The total duration for the clip aggregate.
  • Min. Duration – The minimum clip duration.
  • Max. Duration – The maximum clip duration.
  • Total Msg. Response Time – The total message response time.
  • Min. Msg. Response Time – The minimum message response time.
  • Max. Msg. Response Time – The maximum message response time.
  • Message Response Count – The count of messages responses.
  • Bytes Sent – The sum of the total number of bytes for the test clip sent to the remote server, including the request line, the headers, the body, and all separating whitespace.
  • Bytes Received –The total number of bytes received from the remote server for the clip, 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.

Collection Aggregate

This export contains aggregated information for each chain executed during the test. It contains one row for each clip/chain/error/completion status/Start Time combination regardless of how many times that chain was executed during the second or from which track or band it was executed.

  • Clip Name – The name of the test clip in the test composition.
  • Collection Name – The name of the chain in the test clip.
  • Error – The error text (or NONE if no error).
  • Completion Status – The completion status. For example, Playing or Completed.
  • Start Second – The second when the given chain started.
  • Count – The count for the chain.
  • Total Duration – The total duration for the chain.
  • Min. Duration – The minimum chain duration.
  • Max. Duration – The maximum chain duration.
  • Total Msg. Response Time – The total message response time.
  • Min. Msg. Response Time – The minimum message response time.
  • Max. Msg. Response Time – The maximum message response time.
  • Message Response Count – The count of message responses.
  • Bytes Sent –The sum of bytes sent for the given collection to the remote server, including the request line, the headers, the body, and all separating whitespace.
  • Bytes Received –The total number of bytes received from the remote server for the collection, 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.

Track Aggregate

This export contains aggregated information for each track executed during the test. It contains one row for each clip/chain/error/completion status/Start Time combination regardless of how many times that track was executed during the second or from which band it was executed.

  • Track Name – The name of the track in the test composition.
  • Error – The error text (or NONE if no error).
  • Completion Status – The completion status. For example, Playing or Completed.
  • Start Second – The second when the given chain started.
  • Count – The count for the chain.
  • Total Duration – The total duration for the chain.
  • Min. Duration – The minimum chain duration.
  • Max. Duration – The maximum chain duration.
  • Total Msg. Response Time – The total message response time.
  • Min. Msg. Response Time – The minimum message response time.
  • Max. Msg. Response Time – The maximum message response time.
  • Message Response Count – The count of message responses.
  • Bytes Sent –The total number of bytes sent for the track to the remote server, including the request line, the headers, the body, and all separating whitespace.
  • Bytes Received –The total number of bytes received from the remote server for the track, 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.

Error Aggregate

This export contains lists summary information about message and script activity within that second for only those messages that had an error. There is one row for each second, error combination.

  • Second (Relative) – The second expressed as relative time.
  • Second (Absolute) – The second expressed in absolute time.
  • Error – The error text (or NONE if no error).
  • Message and BrowserActions Count – The count of messages/actions.
  • Send Count – The messages/actions sent for the error.
  • Total Response Time – The sum of all of the error clip element’s duration values for all actions in this container and containers it contains that did complete a request (see the collection's Response Count).
  • Avg. Response Time – The average response time.
  • Min. Response Time – The minimum message response time.
  • Max. Response Time – The maximum message response time.
  • Total Response Time – The total message/action response time.
  • Min. Total Time – The minimum of the Total times for every error.
  • Max. Total Time – The minimum of the Total times for every error.
  • Avg TTFB – The average time to first byte for the error.
  • Avg. TTLB-TTFB – The average time to last byte minus the time to first byte for the error.
  • Bytes Sent –The total number of bytes for the error that were sent to the remote server, including the request line, the headers, the body, and all separating whitespace.
  • Bytes Received –The total number of bytes received from the remote server for the error, 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.
  • Total Errors – The total errors received for the error.
  • Total Scripts - the Total number of scripts executed during the second.
  • Total Error Scripts - the Total number of scripts with errors executed during the second.

URL Aggregate

This export lists summary information about the URLs in a test. There is one row for each URL and error combination. The following fields are included in the exported data&colon;

  • URL Protocol – The transport protocol for the given URL (e.g. HTTP, ftp, etc.).
  • URL Domain – The URL’s domain.
  • URL Path – The remaining path, after root, for the given URL on a domain.
  • Error – Displays the error text (or NONE if no error)..
  • Count – The count for the URL.
  • Send Count – The number of messages successfully sent for this URL.
  • Total Response Time – The total URL response time is the sum of all of the clip element’s for the given URL.
  • Avg. Response Time – The average URL response time.
  • Min. Total Time – The minimum of the Total times for every URL attempted.
  • Max. Total Time – The minimum of the Total times for every URL attempted
  • Avg TTFB – The average time to first byte for the URL.
  • Avg. TTLB-TTFB – The average time to last byte minus the time to first byte for the URL.
  • Avg Bytes Sent –The average of bytes sent for the given URL to the remote server, including the request line, the headers, the body, and all separating whitespace.
  • Avg Bytes Received – The average of bytes received for the URL, 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.
  • Total Errors – The total errors received for the URL.

Page Completions

This export lists summary information about page completions. There is one row for each minute of the test with a separate column for each page. Multiple results can be combined if the tests were run in parallel.

  • Minute of Test – The minute of the test composition as an integer.
  • Time – The minute as date time. For example, "9/12/2011 10:46:00 AM"
  • Page Name – The remaining rows are the page by name, one column each for each distinct page name.

Page Average Durations

This export lists summary information about page average durations. There is one row for each minute of the test with a separate column for each page. Multiple results can be combined if the tests were run in parallel.

  • Minute of Test – The minute of the test composition as an integer.
  • Time – The minute as date time. For example, "9/12/2011 10:46:00 AM"
  • Page Name – The remaining rows are the page by name, one column each for each distinct page name.

Transaction Completions

This export lists summary information about transaction completions. There is one row for each minute of the test with a separate column for each page. Multiple results can be combined if the tests were run in parallel.

  • Minute of Test – The minute of the test composition as an integer.
  • Time – The minute as date time. For example, "9/12/2011 10:46:00 AM"
  • Page Name – The remaining rows are the transaction by name, one column each for each distinct transaction name.

Transaction Average Durations

This export lists summary information about transaction average durations. There is one row for each minute of the test with a separate column for each transaction. Multiple results can be combined if the tests were run in parallel.

  • Minute of Test – The minute of the test composition as an integer.
  • Time – The minute as date time. For example, "9/12/2011 10:46:00 AM"
  • Page Name – The remaining rows are the transaction by name, one column each for each distinct transaction name.

Fundamentals Summary

This export lists summary information about a test. Multiple results can be combined if the tests were run in parallel.

  • Minute of Test – The minute of the test composition as an integer.
  • Time – The minute as date time. For example, "9/12/2011 10:46:00 AM"
  • Page Views – The number of page views for the given minute of the test.
  • ART (ms) – The average response time in milliseconds for the given minute of the test. Response Time is the complete amount of time spent establishing the connection, sending the request, and receiving and processing the response. Excludes any time spent waiting for a connection to be available from the internal connection pool. If no response is received from the server, then this will be 0.
  • VU – The virtual users for the given minute of the test.
  • Throughput (Mbit) – The throughput in Mbits for the given minute of the test.
  • Errors – The errors for the given minute of the test.

 

Basic Info

This export lists summary information about test components in each result exported.

  • Result Name – The name of the test composition result being summarized.
  • Composition name at execution time – The test composition name at start time (remains the same if the composition is later renamed).
  • Path – The item's full CloudTest repository path. For example, /MyCompany Unit Tests/Unis Tests A1 Comp.
  • Status– The composition status (i.e. Stopped, Aborted, etc.).
  • Start – The absolute start time. For example, 1/20/2012 3:06:29 PM.
  • End – The absolute end time. For example, 1/20/2012 3:10:30 PM.
  • Effective Start – The effective start time of the test composition begins when the first message or action is sent. For example, 1/20/2012 3:06:31 PM.
  • Clips –The number of test clips run in the test compostion.
  • Error Clips –The number of test clips that contained an error.
  • Transactions –The total number of transaction containers in the test composition.
  • Groups –The total number of transaction containers in the test composition.
  • Chains –The total number of transaction containers in the test composition.
  • Messages –The total number of transaction containers in the test composition.
  • Sent Count –The total number of transaction containers in the test composition.
  • Error Messages –The total number of transaction containers in the test composition.
  • Total Response Time –The sum of all of the clip element’s duration values for all actions in the transaction and containers it contains that did complete a request (see the collection's Response Count).
  • Max Response Time –The largest value of the clip element¢s duration for all actions in this container and containers it contains that did complete a request (see the collection's Response Count). For example, 3886.
  • Min Response Time –The smallest value of the clip element’s duration for all actions in this container and containers it contains that did complete a request (see the collection's Response Count). For example, 43.
  • Total TTFB –The total amount of time from the start of the request to the first byte being received from the server. TTFB includes the following: establishing the HTTP connection, sending the request to the remote server, and waiting for the first response byte.. For example, 421429.
  • Total TTLB –The total amount of time from the start of the request to the last byte being received from the server. TTLB includes the following: establishing the HTTP connection, sending the request to the remote server, and receiving the complete response. Does not include response "processing" (e.g. de-compressing, etc.).For example, 423409.
  • Bytes Received –The total number of bytes received from the remote server, 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. For example, 57775831.
  • Bytes Sent –The total number of bytes sent to the remote server, including the request line, the headers, the body, and all separating whitespace. For example, 259698.
  • App Actions –The total number of app actions in the test composition. Zero, if none. Refer to App Action.
  • Error App Actions –The total number of app actions in the test composition that contain an error. Zero, if none. Refer to App Action.
  • Database Actions –The total number of database actions in the test composition. Zero, if none. A database action occurs in a Direct-to-Database Testing.
  • Error Database Actions –The total number of database actions in the test composition that contain an error. Zero, if none.
  • Browser Actions –The total number of browser actions in the test composition. Zero, if none. Refer to Browser Action.
  • Error Browser Actions –The total number of browser actions in the test composition that contain an error. Zero, if none. Refer to Browser Action.
  • Checkpoints –The total number of checkpoints in the test composition. Zero, if none. Refer to Checkpoint.
  • Controls –The total number of controls in the test composition. Zero, if none. Refer to Controls.
  • Delays –The total number of delays in the test composition. Zero, if none. Refer to Time Delay.
  • Ifs –The total number of If-Then-Else containers in the test composition. Zero, if none.
  • Nops –The total of NoOp messages in the test composition. Zero, if none. Refer to Creating If-Then-Else.
  • Scripts –The total number of Scripts in the test composition. Zero, if none. Refer to Script.
  • Error Scripts –The total number of Scripts in the test composition that contain an error. Zero, if none. Refer to Script.
  • UI Automation Scripts –The total number of UI Automation Scripts in the test composition. Zero, if none. Not currently supported.
  • Error UI Automation Scripts –The total number of UI Automation Scripts in the test composition that contain an error. Zero, if none. Not currently supported.
  • Switches –The total number of Switch containers in the test composition. Zero, if none. Refer to Creating Switch.
  • Events –The total number of Events in the test composition.
  • Status –The test composition status. For example, Composition stopped.

Clip Element Properties

This export lists clip element property information.

  • Prop Name – The name of the clip element custom property.
  • Prop Value – The value of the clip element property.
  • Count –The count of the given property name as executed in the test composition. For example, where repeats on the clip element exist, the count will reflect that final tally.

Composition Element Properties

This export lists composition element property information.

  • Prop Name – The name of the clip element custom property.
  • Prop Value – The value of the clip element property.
  • Count –The count of the given property name as executed in the test composition. For example, where repeats on the clip element exist, the count will reflect that final tally.

Attachments

    Outcomes