When a performance test is executed, there any many errors that can occur. All error codes are flagged, and you can view them in the Statistics Tab. They fall into the following categories: Connection Errors The HTTP Request to the web server could not be made. Usually this is an error in the name of the web server, a hardware problem, or a network problem. A description of the error will be given in the Playback Error Dialog. HTTP Errors The HTTP specification defines a list of error codes that the web server may return. All error codes that are returned during playback are flagged as errors, and you can view them in the Statistics Tab. A description will be included with each HTTP Error. Error Code Meaning 400 Bad Request 401 Unauthorized 402 Payment Required 403 Forbidden 404 Not Found 405 Method Not Allowed 406 Not Acceptable 407 Proxy Authentication Required 408 Request Timeout 409 Conflict 410 Gone 411 Length Required 412 Precondition Failed 413 Request Entity Too Large 414 Request-URL Too Long 415 Unsupported Media Type 500 Internal Server Error 501 Not Implemented 502 Bad Gateway 503 Service Unavailable 504 Gateway Timeout 505 HTTP Version Not Supported Reply Validation Web Performance TrainerTM provides three ways to validate replies received from the web server during playback. The first method, checking the HTTP response code, has been described above. The replies can also be validated by checking the size of the reply and searching for some text in the content of the reply. When editing a recorded HTTP Request (double-click on the URL in the Record tab), if you select the Validation tab you will see the corresponding screen for configuring reply validation. Size Validation Size Validation checks the correctness of a reply from the web server by checking the size of the returned content. The size can be validated against a minimum value, a maximum value or both. If you select "Greater Than", this means that if the HTML page that is returned for the HTTP Request will be flagged as an error if the size of the page is greater than you figure you give. The reverse is true of the "Less Than" option. Content Validation Content Validation checks the correctness of a reply from the web server by checking for the presence or absence of some text in the returned content. Configuring validation to record an error when some text IS present in the content is useful when the web server will return a page containing some standard content (e.g. an error message) when an error condition is encountered. Configuring validation to record an error when some text IS NOT present in the content is useful when looking for a particular message or keyword in the content to indicate the correct reply. Note that this type of validation is only useful when the content returned from the web server is text, such as HTML, plain text or XML replies. It will not work when the reply is any other content type, such as images or other binary content. It should also be noted that validation of text content is resource intensive -- which means that it will increase the amount of processing power required to run a test...and therefore reduce the number of users that a machine can simulate.

Search