10 Must Do's for testing mobile apps
Download as PPTX, PDF0 likes379 views
The document outlines key aspects to consider when building a test plan for mobile applications, emphasizing elegance, usability, stability, privacy, security, interoperability, performance, content, and overall satisfaction. These ten elements are presented as essential for ensuring quality apps. The author's expertise as a principal advisor in QA and testing supports the recommendations given.
10 Must Do's for testing mobile apps
- 1. Tony Chung Principal Advisor, QA & Test *
- 2. *
- 3. *
- 4. *
- 5. *
- 14. 1) Elegance 2) Usability 3) Stability 4) Privacy 5) Security 6) Privacy 7) Interoperability 8) Performance 9) Content 10)Satisfaction Build your testplan with all Top 10 Must Do’s in mind and you’ll have quality apps!
Editor's Notes
- #4: App analyics Apptentive – in app messaging and communication. Sending star ratings Other tools Crashlytics Flurry App Annie All collect big data, break it down by OS, versions, devices, scrapes the app store reviews, and compiles reports for people to see.
- #5: * needs to look good. this is obvious, but users will stop using it if its ugly. (ie. yahoo sports) . listen to the feedback from users
- #6: Usability - not just visibility, but design issues. left-handed users, simple interface, small hands to reach buttons… * accessibility - large font testing, resizing, as QA, need to consider these test scenarios.red on orange. try testing in high-contrast mode, and you wont see anything (like in the sun) Difficult to navigate (ie. hulu plus, searching movies is hard cause they have so many other things blocking the viewability of the search option) ticks off users, and see app reviews for feedback. users flee hulu and go to netfix cause of users
- #7: Stability - apps crash all the time. upgrade scenario, a few versions back, bugs happen because maybe a data structure is old * crashes before it launches. how to deal with the small 5% crashes with little feedback from users? missing services on an update (ie: images are larger now on newer phones, but app might not be compatible with higher end phones, or looks like crap)hardware layer can cause regressions, new software updates -- break apps looking for reviews help
- #8: 4) Privacy - be proactive with telling users what you’ll do with their data deleting an app doesnt mean the servers will remove your server side data (aka Lyft). discovered by later logging in and realizing CC is saved. Uber asked for location data, and still tracks if your app is closed. that’s scary to users, if its not mentioned (get your GPS location) be respectful of privacy
- #9: 5) Security - concerns of data breach. most are related to login. can’t log in. reset password, still can’t log in. most app teams are using strange characters, and text fields on mobile is filtered out. other languages, dont encode properly. (meaning by the time the password hits the server, its a different character) if a user types the wrong key, they are masked and dont even know they type it wrong. clear text is one way to deal with it. Session Management: Use story of caching sign in page, and getting an interrupted call
- #10: 6) Pricing - overpricing could draw users away from apps. key is to price correctly * determine what you are pricing for. What is the going rate for apps in your category? is it more superior or less than the competition? also look at OS market, and also device screen size (iPad vs iPhones) typically free or 99c. 2.99-4.99 for more complex features Free vs. paid vs . in app. most known apps are free, but promote other paid services (ie. Netflix) Free apps can also use ad based model. target region for apps. $999 for bar exam app. (BarMax) the key to pricing your app is finding a balance between functionality and what users will find reasonable.
- #11: 7) Interoperability - works across all devices, features are parity. expectations support on tablet, devices, and operating systems. apps are fluid with each other, api coverage and compatible. Testing devices work and pair with other devices (phones, tablets, tvs, watches). What about cloud data?
- #12: 8) Performance - startup and load times are under 5 seconds. no latency, lags, slowness of usage. things like pre-caching, content loading, all are relevant. 300ms is what the human brains can perceive.
- #13: 9) Content - content must be updated, modern, and keep the user on the apps. if its a game, it needs to be interesting. if its a productivity app, it must be user experience, parity of usage, and productive.
- #14: 10) Satisfaction - users will come back. user reviews pertain to emotion. its users talking about the app, and not very constructive feedback. but it drives the star ratings about 90% more than any other category.
- #15: 10) Satisfaction - users will come back. user reviews pertain to emotion. its users talking about the app, and not very constructive feedback. but it drives the star ratings about 90% more than any other category.
- #16: 10) Satisfaction - users will come back. user reviews pertain to emotion. its users talking about the app, and not very constructive feedback. but it drives the star ratings about 90% more than any other category.