Performance testing for mobile social apps (OpenFire background XMPP protocol LoadRunner tools)

Background

OPENFIRE/XMPP protocol to build Instant messaging services, corresponding to the Android, IOS mobile applications, want to pass a performance test to verify whether they meet the performance requirements, now the Master tool is LoadRunner, but L2 itself does not directly support the XMPP protocol, The performance test script is now developed through LoadRunner. (In the same way, most mobile apps can script along the following lines of thinking)

Preparatory work

• Wireless card device One-used to create a virtual AP
• 360 free WiFi Latest version-used to bring Android, iOS device traffic to the virtual AP before sending to the server
• WireShark Latest version-used to grab packets of PC NIC traffic
• LoadRunner Latest version-for scripting, consider free within 12.0,50vuser

Specific steps

After connecting the wireless card to the PC, launch 360 free WiFi and create a virtual AP

Then, the installation of the test equipment installed in the app to the WiFi network, this time, the device is the trend of all traffic:

Wireless (Android, IOS)-WiFi "Catch Me"-PC network card---server

Some people will say that actually set up a WiFi network agent on the test device phone, but, remember, not all traffic will go to proxy settings

Some people will say that actually running tcpdump on the test device can capture all the traffic, which is correct, but the tester can't see the traffic in real-time, can see is only a series of business operations after the generation of a traffic log file. pcap

Some people will say that you can use Fiddler, intuitive, real-time, but also can catch package modification package, however, Fiddler can only see HTTP traffic.

After completing the above work, start Wireshark, on the Wireshark home page, you can see a minimum of two network connections, such as:

Regardless of which wireless network connection is correct, select "Local Area Connection", as it is now possible to ensure that the test device's traffic is sent over the PC network Mehsud. Select start to start monitoring:

At this time, enter the filter condition XMPP, and in the test device to perform a series of application business operations, you can see the traffic generated in the Wireshark:

However, what you see is also possible in the following situations:

At this point, change the filter rule to:

IP.ADDR = = < server IP address > && tcp.flags.push = = 1

You can see the corresponding traffic:

adjourned

Performance testing for mobile social apps (OpenFire background XMPP protocol LoadRunner tools)