Playback parameters

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:

In Play <number> iteration(s) of Actions, more than one iteration of an Actions Container can be defined for the execution.
The Use current scenario URL exclusion filter option allows excluding the requests whose URL corresponds to one of the regular expressions in the exclusion filter from the scenario and ignoring them during the test playback.
The Play User Path defined think times option includes think times in the playback. The Enable page rendering during validation sub-option displays pages in HTML automatically.
When the Enable the calculation of the responses difference rate option is checked, NeoLoad identifies the level of differences between the record responses and the playback ones. In the Check User Path dialog, the Difference column lists the pages with potential response issues.
It is recommended to deactivate the option when checking a large User Path.
When the Enable full data retrieval for POST requests option is checked, NeoLoad stores the full response of POST, PUT and DELETE requests.
It is recommended to leave the option disabled when checking a large User Path.
The Clean Shared Queue variables at the end of the validation option allows to automatically clear "Shared Queue" variables at the end of the User Path check.

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.

Warning:
The Virtual User whose check file has been exported must be in the same state (requests, logical actions, etc.) at import as it was at export time.
A Virtual User check file can be imported only after an export performed in NeoLoad 5.5.

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.

When the Check User Path dialog displays a Difference percentage, you can get a compared view on the selected element with a click on the Compare with recording button or with a double-click on the Difference cell. The Comparison dialog that pops up includes icons to switch between requests, changes, and blocks. See Compare requests and responses.

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

for the entire User Path with:

a right-click in the User Path, then a click on Update Recorded Content, or
a click on the Advanced button, then on the Update button in the Advanced Parameters dialog

for selected pages in the User Path tree:

with a right-click on a selected page, then a click on Update Recorded Content

Alerts are raised when:

requests cannot be played
errors are detected

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%.

Updating the recorded content of a User Path is definitive and cannot be reverted. To back up a User Path before it is updated, you can export it, as described in Export.

To update the recorded content of a User Path

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

Home