Debug Virtual Users

For this feature to work, set the On Error scenario setting to command LoadNinja to enable the debug mode:

1. Go to Projects and click your project in the list:

   

   Click the image to enlarge it.

2. Switch to the Load Test Scenarios tab and then click your scenario:

   

   Click the image to enlarge it.

   Tip:	Use the search box to filter the scenario list. It allows searching for a specific character in a scenario name or for a specific date.

3. On the Error Handling panel, in On Error, select Debug Error:

   

   Click the image to enlarge it.

4. In Debug Time, specify for how long a virtual user must stay in the debug mode on errors.

   If the debug time passes with no actions from your side, LoadNinja commands a virtual user to end this particular iteration of a script run and launch the next one. To learn more about how LoadNinja runs tests, see Scenarios.

After this, on all subsequent load test runs of this scenario, a virtual user will enter the debug mode when the issues occur.

To debug errors:

• Interact with the virtual user on the results screen for the test run which is in progress. Wait until LoadNinja opens this screen automatically on the test start.

  — OR —

• Select the needed test run on the Dashboard:

  

  Click the image to enlarge it.

  — OR —

• Open the test results screen from the Projects > Test Runes page.

  See instructions

  See instructionsSee instructions

  1. Go to Projects.

  2. Click the needed project in the list.

     

     Click the image to enlarge it.

  3. Switch to the Test Runs tab.

  4. Locate the needed test run in the list, then click it.

     

     Click the image to enlarge it.

     Tip:	Use the search box to filter the test runs list. It allows searching for a specific character in a test run name or for a specific date.

When the results screen opens up, switch to the Errors tab:

Click the image to enlarge it.

The Errors tab lists all errors that occurred during the test run.

Learn more about error records

Learn more about error recordsLearn more about error records

Each error record includes the following information:

Field	Description
Time	The date and time when the error occurred.
Script	The script the virtual user was performing when the error occurred.
URL	The URL of the tested service.
Step Name	The name of the step in the script.
Address	The IP address of the tested service.
User	The number LoadNinja uses to identify the virtual user which encountered the error.
Iteration	The serial number of the iteration the virtual user was performing.
Response Code	The HTTP code of the response (if available).
Error Message	The message describing the error.

Use buttons on the right of an error record to perform debugging:

• Show Image — Show the page as the virtual user sees it when the error occurs.

• View Network Traces — Show the network traces. Available for HTTP errors only.

• Debug Mode — Open the debugging page for a virtual user which encountered the error.

• Download HTML — Download the copy of the page in the state it was when the error occurred.

  Note:

  This downloads only the .html file, without including any images or assets.

Navigate through error records

In the debug mode, analyze the state of the page a virtual user was interacting with when the error occurred.

Click the image to enlarge it.

• On the page’s toolbar, check the IP of the virtual user to make sure the firewall or routing rules of your service allow this virtual user to access the service.

• In the frame, view the URL and current state of the page.

• Use the JavaScript Terminal to send various commands to the service.

  LoadNinja provides full access to the tested page’s DOM via the document object, so you can access web page elements in the same way as regular JavaScript uses in web pages:

  JavaScript

  // Get an element by ID
  var obj = document.getElementById("elem-id");
  
  // Get the inner HTML code of the last element
  var data = document.body.lastChild.innerHTML;

  To access various objects, use buttons on the terminal’s toolbar:

  •  — Get the page’s title.
  •  — Get the page’s URL.
  •  — Get the page’s content as an HTML code.

• At the page’s bottom, view the network traces.

View Network traces to identify the source of the issue that your virtual user encountered. Access them:

• On the Debugged tab of the results screen.
• In the debug mode.

The network traces panel is a table that contains URLs of all resources (pages, images, scripts) the virtual user tried to access during the iteration and timings for these URLs. All resources the virtual user had trouble accessing are marked with the icon.

Click a URL in the list to view extensive information about an operation:

Click the image to enlarge it.

The General tab

The Request tab

The Response tab

The Timings tab

The Raw Data tab