Some native applications cannot be recorded in proxy mode. When the mobile device does not support the definition of a proxy or when the application cannot use the defined proxy, it is necessary to use the tunnel mode. This mode makes it possible to record any mobile application, either web or native, standard or customized, for any platform in any version.
The communication between the mobile device and the server is recorded through the NeoLoad Tunnel function which makes it possible to launch the NeoLoad Recorder without using the NeoLoad proxy. On one side, the Tunnel simulates the web server for the mobile device, and on the other side, it processes the requests and responses with the web server. The Recorder catches the transactions to build the scenario. NeoLoad allows the filtering of the recording to skip or include some requests in order to get an accurate scenario.
You can start recording an application with:
Warning: Before recording the scenario, it is recommended to close all HTTP client applications (other Web sessions, Twitter client, and so on). NeoLoad records all the HTTP flows going through the machine. It is necessary to close HTTP clients or define exclusion rules in NeoLoad to avoid unwanted requests in the recording.The Start Recording dialog makes it possible to define the new recording.
To record in tunnel mode, the tunnel mode option must be selected.
It is recommended to uncheck the Start client option as the mobile device itself generates the traffic. As soon as the record is started in NeoLoad, the mobile application can be used. NeoLoad catches the HTTP traffic of the recorded application to create the test scenario content.
A click on the OK button closes the Start Recording dialog and displays the Tunnel mode recording wizard to prepare the recording.
A click on the Detect servers button starts the native application discovery function.
The Detecting servers bar shows the IP address of the NeoLoad Controller. Without closing the bar, the IP address of the DNS server of the device must be modified to reroute transactions toward the NeoLoad Controller:
At that moment, the application on the mobile device must be started to have NeoLoad detect the servers used in the application. On the mobile device, every action in the scenario must be performed to have the Detecting servers bar analyze the application.
A click on the Stop server detection process icon closes the Detecting servers bar and updates the Tunnel mode recording wizard. The Servers list step displays all the application servers and domains to record:
The servers list can be modified with the Add and Remove buttons. It can be modified subsequently too at the end of the scenario record or in the Design section.
In the Tunnel mode recording wizard, clicking the Next button launches the Configuration check step.
When issues are raised, it is necessary to correct them before starting the true record of the application:
On Windows Seven for example, it is necessary to choose Control Panel > Network and Sharing Center > Local Area Connection > Properties > Internet Protocol Version 4 (TCP/IPv4) > Properties > Advanced to display the Advanced TCP/IP Parameters dialog. In the IP addresses section, a click on the Add button allows specifying the first IP for the identifiers range, for example
192.168.1.210. All the parameters must be saved for the new virtual IP addresses to be taken into account.
Once IPs and ports are ready, clicking Back in the Tunnel mode recording wizard makes it possible to restart the Configuration check step. When the configuration is ready, a click on the Finish closes the wizard.
The Recording of Virtual User bar is displayed to record the mobile application. To make sure the DNS server is used when recording the application, the mobile device must be restarted.
Browsing the application and performing every action of the scenario automatically create the record in NeoLoad. When all the actions are done, a click on the Stop Recording icon stops the recording and closes the recording bar. The Post-recording Wizard opens up to help configure the recorded scenario. For more information, see Post-recording wizard. Subsequently, the scenario can be edited and improved in the Design section of the NeoLoad Controller. For more information, see User Paths.
When the recording is over, the original IP address of the DNS server must be set back on the mobile device before restarting it to save the change.
neoload.logfile : The log keeps track of the original DNS configuration before it is modified for the tunnel mode. For example:
2012/11/13 09:27:20 INFO - neoload.DNS: Original DNS server IP is : 192.168.1.4
2012/11/13 09:27:20 INFO - neoload.DNS: Original DNS server is configured by DHCP : false