Problems detected by Root Cause Analysis

The detected problems are listed by category:

Availability

Byte Limit Exceeded failures

  • Byte Limit Exceeded failures occur when the overall size of retrieved objects for a page exceeds the allowable threshold as set by the testing agent.
  • Root Cause Analysis lists the top objects that contributed to the Byte Limit Exceeded error. The objects are presented in order of object size by number of bytes.

Client errors

  • Client errors represent problems with the page content loading once the connection to the host is established. The action error code provides the specific reason for the client issue.
  • Root Cause Analysis lists the top actions that were being processed by the test when the client error occurred. The failing actions are presented in order by processing time. The return code indicates the error that was observed for this action.

Content Mismatch errors

  • Content Mismatch errors are page failures that are triggered by the existence, or lack of, of certain keywords or phrases in the page results.

  • Root Cause Analysis lists the test time of the latest test execution that resulted in a content mismatch error. The failed validation string is provided. It also indicates that if that test execution contained content errors on that page, or any previous page, and lists the page content errors that were observed.

DNS Lookup errors

  • DNS Lookup errors are page failures that are associated with the inability to resolve the providers server host name to an IP address in order to establish a connection to that host.
  • Root Cause Analysis lists the top actions that were being processed by the test when the DNS lookup error occurred. The failing actions are presented in order by processing time. The return code indicates the error that was observed for this action.

Network errors

  • Network errors represent page failures resulting from an inability to establish a connection to a specific host provider or the inability to maintain that connection during the entire test execution. The action return code provides the specific reason for the network related failure.
  • Root Cause Analysis lists the top actions that were being processed by the test when the network error occurred. The failing actions are presented in order by processing time.

Redirection errors

  • Redirection errors represent page failures associated with the redirection of the original page object to an alternative location. The action error code provides the specific reason for the redirection error.
  • Root Cause Analysis lists the top actions that were being processed by the test when the redirection error occurred. The failing actions are presented in order by processing time. The return code will indicate the error that was observed for this action.

Server errors

  • Server errors represent page failures that are attributed to a problem within the host provider server infrastructure. The action error code provides the specific reason for the server failure.
  • Root Cause Analysis lists the top actions that were being processed by the test when the server error occurred. The failing actions are presented in order by their processing time. The return code indicates the error that was observed for this action.

SMS errors

  • SMS Send/Receive errors represent page failures that are attributed to a problem associated with the delivery or receipt of a text message as part of the test script. The action error code provides the specific reason for the SMS failure.
  • Root Cause Analysis lists the top actions that were being processed by the test when the SMS send/receive error occurred. The failing actions are presented in order by their processing time. The return code indicates the exact error that was observed for this action.

Test Abort errors

  • Test Abort errors are page failures that resulted from an aborted test execution.
  • Root Cause Analysis lists the top actions that were being processed by the test when the test abort occurred. The failing actions are presented in order by processing time. The return code indicates the error that was observed for this action.

Content Wait timeout

  • A Content Wait timeout occurs when the page load process is waiting for the existence of an object in the results and the wait time exceeds the maximum allowable time limit as set by the testing agent.
  • Root Cause Analysis lists the test time of the latest test execution that resulted in a content wait timeout error. It also indicates if that test execution contained content errors on that page, or any previous page, and lists the page content errors that were observed.

Execution timeout

  • An Execution timeout occurs when the total test execution time for a page load or object retrieval exceeds the maximum allowable time limit as set by the testing agent.

  • Root Cause Analysis lists the top actions (object retrieval or connection times) that contributed most to the execution timeout error. The actions are presented in order of page contribution percentage. The page contribution is calculated by dividing the action response time by the overall page response time.

User Script errors

  • User Script errors are page failures that occur during the execution of the test script where the script can no longer perform the necessary actions required.
  • Root Cause Analysis lists the test time of the latest test execution that resulted in a user script error. It also indicates if that test execution contained content errors on that page, or any previous page, and lists the page content errors that were observed.

Performance

Page response time increase

  • The overall page response time variance (max - min) for successful page runs has exceeded the minimum threshold that was established for problem identification.
  • Root Cause Analysis lists the top actions (object retrieval or connection times) that contributed most to the page response time increase. Actions are presented in the order of page contribution percentage. Page contribution is calculated by dividing the action response time by the overall page response time.

Page content

Object count increase

  • The overall page object count variance (max - min) for successful page runs has exceeded the minimum threshold that was established for problem identification.
  • Root Cause Analysis lists the top providers that contributed most to the page object count increase. Providers (hosts) are list in order of their increased object count contribution for successful tests executed during the analysis window.

Page size increase

  • The overall page object size variance (max - min) for successful page runs has exceeded the minimum threshold that was established for problem identification.
  • Root Cause Analysis lists the top providers that contributed most to the page size increase. Providers (hosts) are listed in order of the increased object size contribution for successful tests executed during the analysis window.

Uncategorized page failures

  • Uncategorized page failures are failures that cannot be classified into the other standard Availability categories. The error code indicates the reason for the failure.

  • Root Cause Analysis lists the error return code for test failures that were not classified into any existing Availability error category.