Identify the request containing the error

Depending on the application tested, requests return the HTTP 500 Internal Error code. In this case, NeoLoad automatically flags the request as containing an error.

In many cases however, the error is handled at the application level and the page returned by the server shows a 200 OK error code. In this case, NeoLoad cannot detect the error automatically, and the error must be searched for manually.

• To search for an error manually

1. Run the Virtual User validation. See Run the Virtual User validation.
2. Scan all the requests with HTML responses. Typically, these will be the first or second response in each page.
3. Check the response content for each HTML request:
   • Click on the request
   • Make sure the Response option box is checked in the Details section.
   • Examine the server response displayed in the text area for any error message or inappropriate content. Click Open in browser to display the response in a more readable format, then click Compare with recording to highlight the discrepancies between the replayed request and the response received during the recording.

In the example, the 500 Internal Error code clearly identifies the request containing the error.

• Warning: When an error occurs, it usually triggers a cascade of subsequent errors. To correct the problem therefore, it is important to work on the first request containing an error. Once this has been fixed, run the Virtual User validation again and correct any other errors that may be flagged.

Home