Mobile Application Testing Strategy – INDUCIBLE SIGNALS
1. I – Integration
· To understand User Integration aspects for
Mobile Applications across API’s, within the device and many other integration
aspects that actions the behaviour of the mobile application
· To verify various user types and workflows that
define the objective of the application
·
To verify usability aspects for the workflows
2. N – Notification
· To understand all possible
notifications
·
To test the read and unread notifications and
behaviour on those notifications for mobile apps
3. D – Device & Platform
·
To understand User Integration aspects for
Mobile Applications across API’s, within the device and many other integration
aspects that action the behaviour of the mobile application
·
To verify various user types and workflows that
define the objective and principle of the applications
·
To verify usability aspects for the workflows over different Devices and Platforms
4. U – User Stories & Usability
·
To understand User Scenarios and Usability for
Mobile Applications
·
To verify various user types and usability aspects for the workflow that
define the purpose of the applications
5. C – Conformance
·
To understand various conformance parameters for
making the application available on the different market places
·
Android market place conformance guidelines
·
iOS market place conformance guidelines
·
Windows mobile market place guidelines
6. I – Interrupts
·
To understanding the impacts of interrupts like
voice calls and messages etc. while the app is running
·
To verify app behaviour under the influence of
various interrupts for mobile
7. B – Browser
·
To understand the importance of multiple browser
testing for web apps and hybrid apps and their interactions with the native
apps if any
·
To verify web apps using browser
8. L – Location
·
To understand Locations aspects like – GPS and
its impact if any for Mobile Applications
·
To verify Location specific aspects for mobile
9. E – Efficiency
·
To understand efficiency/performance aspects for
Mobile Applications – like usage of CPU, Memory and other resources
·
To verify performance and efficiency for mobile
apps
·
Use of third party tools for measuring
efficiency/performance parameters
·
Competitor performance benchmarking
10. S – Synchronization
·
To understand that the mobile apps can be
accessed across different and multiple devices at any given time, the need to
synchronize the data across various platforms and devices and test the same
11. I – Interactions
·
To understand interactions including starting
the app, shutting down the application, performing various actions on the
applications using the user interface
·
To verify various interactions for mobile apps
12. G – Gesture
·
To understand various Gestures for Mobile
Application
·
Touch events
·
Drag and drop
·
Multi-touch actions
·
Long press, Pinching, expanding actions and many
more
·
Testing various Gestures’
13. N – Network
·
To uderstand network related aspects that can
impact the reliability and availability of the mobile app
·
To verify resilience and availability due to
network issues
14. A – Accessibility
·
To understand (ADA-509) Accessibility aspects for Mobile
Applications
·
Tp verify Accessibility for mobile
15. L – Localization
·
To understand impact of languages and their
usability aspects for Mobile Applications
·
To verify simple localization areas for mobile
16. S – Security
·
To understand the importance of securing the
data across various devices
·
To verify security aspects for mobile
18. U – Updates
·
To understand how mobile apps updates, OS level
updates can impact the existing user base
·
To verify to reduce the risk associates with
updates and ensuring updates happen seamlessly
17. O – Orientation
·
To understand the mobile application behaviour
when the orientation changes from landscape to portrait mode. Various other
orientation related aspects and verifying the same
18. T - Traffic Analysis & Splash Time
·
To understand the mobile application behaviour
when estimated traffic is consistently active. Various kinds of spike, sudden
surge like Big Billion Day, Black Friday Sale, New Launches like iPhones, etc.
·
Using third part tools for measuring and
improving the application threshold and benchmarks.
