I had tested web applications with LoadRunner 9.51 but first time I got a mobile application for performance testing. Don't have much clarity on this any idea would be appreciated. [img]/images/graemlins/confused.gif[/img]
You have two paths for mobile applications, either it is WAP or it is not. WAP is a specialized dialect for low bandwidth situations where a WAP gateway is involved to translate standard html to the WAP dialect, or it's just a straight application, such as a mobile site with HTTP/XML under the covers. You need to find out which type of application you are using.
Once you find out then you need a device emulator that you will record against as a standard application. Or, if you are lucky you can just connect to the mobile site from your standard browser and record the actions in question.
Cultivate your architectural eye. Pick up copies of the system design documents (SDD) and system requirements documents (SRD) to find out if WAP is involved. Ask your developers and functional testers which device emulators they are using on their development boxes.
Lastly consider your network infrastructure issues. Have you considered something like Shunra's appliances to emulate the low bandwidth and shared bandwidth situation that your applications are likely to encounter in the field? What is the difference in performance between a 3G, 4G and wiFi connected device in terms of response time? Well, you can see where this is headed.
WAP is pretty much dead these days, I wouldn't be concerned much about it.
There are some plugins for Firefox which allow it to emulate different kinds of mobile browsers, though I'm not sure they do much more than merely replacing the User-Agent header, which, in most cases, is enough.
Another possibility is to record the mobile device itself using proxy mode of VUGen (there is an assumption that the device can connect to the VUGen machine using TCP/IP). This is a more reliable method, as it captures the real browser traffic, and not any emulator/plugin/other kind of surrogate.