September 16, 2014 at 9:49 am #4086
Yeah – they both run Android. Like most smaller manufacturers devices these days.September 16, 2014 at 10:18 am #4089AfreenParticipant@ahossain
Thanks a lot for the great presentation! I agree with you on many points and have taken similar approach while releasing mobile apps. Can you suggest a good tool that will help load testing on mobile?September 16, 2014 at 10:20 am #4090
Will you be testing a mobile app or website?September 16, 2014 at 10:45 am #4093DanParticipant@danielbilling
I can vouch for Bill’s expertise. I sat in on a course he delivered at LTGW last year, and also at Ministry of Testing.
You might want to consider proxying not only via Fiddler, but also through OWASP Zed Attack Proxy…use with caution though @Andy.September 16, 2014 at 12:00 pm #4109September 16, 2014 at 12:07 pm #4112
I’ve heard good things about Blaze Meter http://blazemeter.com/. It does depend though on how much of the work is being done by the mobile client rather than the server, If most of it’s server side then you’d be better deploying one of the popular desktop load testing tools instead (which are more mature).September 17, 2014 at 9:36 am #4145PadmarajParticipant@padmaraj
@Stephen & All,
In my point of view and in my experience, the best practice with mobile app testing are::
1) Manual/Automation tests – By Testers
2) Unit Testing – By Developer
3) Integration Test – (Developer/Tester)
4) Test Environments – ( Dev Test / Pre Prod Test / Production Test )
5) Device Coverage – Depend on version compatibility ( Own Internal Lab, Cowed source testing, Open device lab )
- You must be logged in to reply to this topic.