Analyze errors on a scenario run

Running a particular scenario will produce statistical results and provide a comprehensive list of all the errors (and assertions failures) occurring during the scenario run. The following screenshot shows the content of the Errors tab in Results mode after having run a particular scenario. As mentioned earlier, the information shown in this tab is very similar to that shown in the Check Virtual User dialog box.

Errors are also displayed by NeoLoad in Runtime mode during a scenario run, in the Runtime Errors tab.

The following points are where the Check Virtual User dialog box and the Errors tab differ:

The rest of this section details how the new elements provided by the Errors tab can be used.

Filtering and Sorting by Virtual Users

In the example, you may want to analyze the 500 error generated on the OccasionnalUser Virtual User. You may also want to concentrate on a particular user of this type, the OccasionalUser#5.

Using the Previous Request

In the example, the GET request /loadtest/error has returned an HTTP 500 return code. This is the following error code : Internal Servlet error.

If you take a look at the previous request by selecting the previous request radio button , you understand that the loadtest/redirect/simple.jsp page has been requested.

You can now push your investigation a little further and display the response returned by the previous request by selecting the previous response radio button.

The response contains a 302 Moved Temporarily code redirecting the client Agent to the page called loadtest/error. The problem is therefore in the loadtest/redirect/simple.jsp which redirects to an error page. This simple example shows you how to meaningfully use the information NeoLoad provides concerning the context in which an error occurs.