We have a native mobile application that would be accessed within a localized Wi-FI guest network. A web mobile farm would not work as it would not be able to access the localized Wi-Fi guest network. What have been the best experiences for users with native mobile performance testing?
The question can be answered many ways, but what you really need to do is to account for the lowest common denominator of each variable. If you want to use a Mobile farm, you still can by profiling the Wi-Fi and using this as a test parameter. If you're more interested in "real" devices, then you can leverage the oldest allowed devices with a bunch of background apps, and also plug this into a mobile farm. If you can account for both of these variables, you can all but guarantee predictable performance outcomes. Try solving the quandary and then tools can be applied freely without opinion. :-)
Good day,
Actually, Ive synchronised my principal database from HQ with the one at the DR site by use of mirroring. They both run on SQL Server 2008. I would like to test the accessibility of the data being replicated at the DR site. What test tools can I use to confirm that indeed that data is readily available and accessible in terms of disaster; apart from having to restore the db at the DR site and allow it to be on read/write mode?
Thank you.
Keneilwe (System Analyst)
Eggplant tool would be best option for conducting native app testing on real device, we are using this tool for our existing customers.
Hi,
I would recommend that this person check out BlazeMeter. They provide performance testing solutions for mobile:
www.blazemeter.com
Radview WL has been my best experiences for users with native mobile performance testing.
Raview WL has been my best experiences for users with native mobile performance testing
Hi,
For the performance testing of native mobile application, best approach is -
1.Create proxy using blazemeter recorder
2.Configure your mobile phone with same proxy
3.Start capturing request with blazemeter recorder as per action performed on mobile application
4.Stop recording and generate .JMX file from same UI
5.Launch Jmeter and open newly created JMX file
6.Run test on Jmeter and you are ready to go :)
Below url will give you detail info:
guide.blazemeter.com
a.blazemeter.com
Thanks & Regards
Poorvaja Deshmukh
For the performance testing of native mobile application, best approach is -
1.Create proxy using blazemeter recorder
2.Configure your mobile phone with same proxy
3.Start capturing request with blazemeter recorder as per action performed on mobile application
4.Stop recording and generate .JMX file from same UI
5.Launch Jmeter and open newly created JMX file
6.Run test on Jmeter and you are ready to go :)
Below url will give you detail info:
guide.blazemeter.com
a.blazemeter.com
What type of reporting do you need ? What are your goals of testing ? Why do you want to do on real devices ? JMeter is an opensource tool you can work with depending on your requirements. Considering a tool entirely depends on your testing requirements. You can also use Smart Bear . If you can afford the licensing then use Load Runner (True Client protocol). you can see the details on this page . community.saas.hpe.com
If you are looking to test the mobile side, I would recommend PerfectoMobile. For server (API) testing, you can go with SmartBear or JMeter.
Load testing will be against the server I presume. Some tools can be installed behind the firewall to do this, capture the HTTP traffic from your mobile device, and create scripts for you by using the mobile native app. I know Appvance UTP does this natively and sets you up to data-drive 1000's of virtual users (full disclosure - I work there) but there may be others as well.
All the performance testing solutions will work with native mobile applications.
Neotys
LoadRunner
JMeter
Soasta
Thanks.