From Web to mobile testing... Evolve yourself

Key considerations when moving from Web application to mobile testing

Transcript

1. E v o l v e y o u r s e l f FROM WEB TO MOBILE - Sandhya Sasidharan
2. EMBRACE THE MOBILE MIND SHIFT ▫︎More and more business is becoming mobile centric 2 ▫︎Having an Application on Mobile means ‣ It is much more closer to the user, allowing better business opportunities and mobility during operations
3. KEY DIMENSIONS ▫︎Usability Testing ▫︎Testing Non-Functional requirements ▫︎Functional testing 3
4. USABILITY TESTING ▫︎Usability plays a key role in motivating/de-motivating the user to continue using the application ▫︎Web Based ‣ Actions are Mostly point and click (mouse) ‣ And keyboard ‣ Pretty well Standardised monitor sizes and resolutions ▫︎Mobile ‣ Usability patterns are different across platforms ‣ Screen sizes and resolutions vary enormously ‣ Portrait and Landscape mode 4
5. USABILITY TESTING ▫︎User Inputs ‣ Touch and non-touch screens ‣ Voice enabled ▫︎Responsiveness ‣ Experience on mobile is much more personal than web ‣ “Instantaneous” is the benchmark 5
6. IDENTIFY YOUR DEVICES 6 ▫︎Understand your target users ▫︎Fast Changing and humungous market ▫︎Narrow down of definitive set of devices ▫︎Choose the right range of devices to test ‣ Highest and lowest screen resolutions ‣ Across platforms ‣ Take advantage of emulators available
7. TESTING NON FUNCTIONAL REQUIREMENTS ▫︎Mobile devices are uniquely constrained in several aspects such as processor speed, memory, multi-tasking support, available network bandwidth, screen real estate. ▫︎Mobile applications need to operate successfully (or degrade gracefully) within a wide spectrum of operating conditions. ▫︎Mobile applications might need to interact with the device’s sensors. - The application must respect the sensor’s operating characteristics. 7
8. ▫︎Space consumption ▫︎App Installation and Upgrade ▫︎Data storage (client and server side) ▫︎Performance ▫︎CPU and Memory consumption ‣ Normal usage ‣ Idle run (with screen lock and power saver mode on/off) ▫︎Multi-tasking ecosystem ▫︎Network ‣ Online and Offline Mode support ‣ Preferred Network channel 8 TESTING NON FUNCTIONAL REQUIREMENTS
9. TESTING NON FUNCTIONAL REQUIREMENTS ▫︎Compatibility ‣ Mobile OS versions, Third party libraries, Hardware, sensor firmwares ▫︎Security ‣ Insecure Data storage and Data leakage ‣ How critical is the data handled? ‣ Devices can be shared among individuals ‣ Weak server-side controls 9
10. FUNCTIONAL TESTING ▫︎Apart from regular feature tests, be conscious about the following: ‣ Screen lock behaviour ‣ Offline mode behaviour ‣ How the feature resumes after interruptions 10
12. Questions? THANK YOU