Nuance of mobile testing jan 23
Download as PPTX, PDF0 likes112 views
The document discusses the modern definition of a Quality Analyst (QA) in mobile testing, emphasizing the need for efficient app design that meets business requirements across various devices and platforms. It highlights the differences between mobile apps and web apps, particularly in terms of database integration, upgrade mechanisms, and the importance of handling multiple OS and app versions. Additionally, it stresses the significance of data migration, offline functionality, and robust error handling to ensure app reliability during updates.
Nuance of mobile testing jan 23
- 1. Nuances of Mobile Testing ThoughtWorks 23 Jan 2018 1
- 2. Modern Day definition of Quality Analyst QA is the one who ensure the app/application caters the user's business requirements in the most efficient way without any disconcert. Cater Business Need Efficient and Performant Without any Disconcert
- 3. General things we think about Mobile testing The Different screen size or Resolution testing? e.g Small phone to bigger phones DESIGN + TECH Native or Hybrid app, Online or Offline Support Landscape and Portrait Platform Centric Design i.e iOS or Android Business Dependency Understanding the Business and its dependency
- 4. Different Screen Size Allign design and Business features which will support all devices extra-large Tech Normal LargeSmall iOS Android Business
- 5. Mobile is different from mobile in various aspects • Browser is not much OS independent VS Mobile apps always dependent on OS • Web apps depend on server side db VS Mobile apps have integrated DB (SQLLite vs. Core Data) • Web apps do not need any upgrade Mechanism VS Mobile Apps have to have strategic upgrade mechanism Have Mobile centric design
- 9. iOS Menu Bar
- 10. Support for Native Functionality of phone Irrespective of app behavior native functionality of phone like Calling and message functionality should not be affected.
- 11. DB modelling and migration Mobile apps are always said to be upgraded due to various reasons * Business functionality * Technology upgrade * OS related upgrades Due to above reason the app needs to be keep on updated During these update we need to ensure the smooth transition of DB
- 12. DB modelling and migration Consider the below example of Profile data in DB Older model consists of one data which consist of Name, Phone and Email New model consists of seprate table for Name, Phone and Email When the app launches the latest code will try to fetch the data from each table
- 13. DB modelling and migration Some apps supports offline functionality predominantly Example: Evernote, One Note, Expensemanager These will have offiline data, like user details etc During upgrade, we should be cautions of syncing the local data to the user persona Install and then resync the data
- 14. Supporting multiple OS version
- 15. Supporting multiple app version Supporting multiple version of app is very important, As we will not sure of how much of users will upgrade to the latest app. Service A App Version 5.0 Service B 2.1 Service B App Version 6.0
- 16. Handling of external dependencies We need to ensure that app doesn’t crash when one of the external dependent service is not available. We need to handle all the possible error handling.