Playback parameters

In the Advanced Parameters dialog, the Playback parameters group box makes it possible to modify the functional conditions of the User Path used during the validation process:

Export

With the Export button in the Actions group box, the current Virtual User check may be exported. In this case, NeoLoad creates an XML file containing all the sent requests, the server responses as well as the Load Generator log file. This may be useful for analyzing a script or when contacting the technical support team. Below is a sample of an XML export:

<?xml version="1.0" encoding="UTF-8" ?> 
<Project user="JPetStore" population="Check-JPetStore-Population" lghost="localhost"> 
    <StartContainer checkID="0" timestamp="703" objectID="2" objectName="JPetStore"> 
    </StartContainer> 
    <StartContainer checkID="1" timestamp="797" objectID="3" objectName="Index" 
        size="1161" duration="109"> 
        </StartContainer> 
    <StartPage checkID="2" timestamp="860" objectID="4" objectName="/jpetstore" 
        size="1161" duration="109"> 
    </StartPage> 
    <Transaction checkID="3" timestamp="1000" objectID="5" objectName="http_1" 
        size="1701" duration="31"> 
        <Request binary="false"> 
            <Body><![CDATA[GET http://host/jpetstore/ HTTP/1.1...]]></Body> 
        </Request> 
        <Response code="200" type="text/html; charset=UTF-8"> 
            <Headers><![CDATA[HTTP/1.1 200 OK...]]></Headers> 
            <Body><![CDATA[...]]></Body> 
        </Response> 
    </Transaction> 
    ...
    <LoadGeneratorLogFile fileName="VirtualUser.zip" nbEntry="1"> 
2012/08/20 12:00:08 INFO - neoload.LG_INFO: Starting LoadGenerator... 
... 
    </LoadGeneratorLogFile> 
</Project>

Import

NeoLoad allows importing a Virtual User check that has been exported in XML format with a click on the Import button. The file to be imported can then be selected.

Update recorded content

The Check User Path dialog helps you identify the number of changes between the recorded scenario and the checked one, and to pinpoint every change in the application with the Compare function, for example changes in paths, in URL arguments, in AJAX calls, and so on. The Update Recorded Content function makes it possible to merge the changes in the User Path, and synchronize it with the latest version of the application. It is particularly useful for test script maintenance.

The Update Recorded Content feature is available in the Check User Path dialog:

Alerts are raised when:

Errors must be fixed in the User Path definition, as described in Check a User Path.

A click on the Overwrite button updates the entire User Path to the current application, except for the requests which cannot be played. In the Check User Path dialog, the Difference column shows 0%.

  1. Select a User Path and start a User Path check.
  2. In the Check User Path dialog, click Start checking.
  3. Right-click the User Path tree, and, when differences are detected, click Update Recorded Content.
  4. Click Overwrite to confirm the update.