Generic test plan
Download as DOCX, PDF1 like480 views
The document outlines a checklist for testing a mobile app. It includes 14 sections for testing installation, uninstallation, upgrades/downgrades, network scenarios, interrupt scenarios, low memory, user interface, functionality, low battery, performance, starting/restarting the app, exiting the app, killing the app, and push notifications. The checklist provides specific test steps to validate the app's behavior under different conditions and ensure proper functionality.
Generic test plan
- 1. Author:- Anubha Mahajan VERSION:- 1.0 Checklist for Mobile App Testing
- 2. 1. INSTALLATION Verify that application can be installed successfully. Verify the behaviour in case of low memory condition. Verify the behaviour if phone switch off during installation. Verify the behaviour if App installed on Android/IOS lower versions (versions for which app not developed). 2. UNINSTALL Verify that application can be uninstalled successfully. Verify that all app data is removed when the app is uninstalled. Move application to Memory card and uninstall the app. Remove memory card and try to uninstall app. Uninstall during app during charging /low battery app. 3. UPGRADE/DOWNGRADE Notification when new version of app available for update and user is successfully able to update to new version with updated version. Proper working of application after updation. Verify the Behaviour of the app when there are multiple updates available. What happens if user don’t update. Verify that if the user is able to downgrade the app. 4. NETWORK SCENARIOS Verify the behaviour of application when there is Network problem and user is performing network related operations. Behaviour of app on 2G/3G network. Response time of user actions in case of WIFI/2G/3G. Behaviour of the app when it switches between networks (Wi-Fi, 3G, 2G). App should not exit or quit forcefully in case there is no network. Response time on multiple devices. (Different Android and IOS versions) Behaviour of the app when device not connected to WIFI/2G/3G. Behaviour of the app when some data is entered and network goes, does the data stay when device is again connected to network or it is reset. Behaviour of the app when data is off but session is created. 5. INTERRUPT SCENARIOS While application is running, perform actions like: Incoming and Outgoing SMS and MMS. Incoming and Outgoing calls. Incoming Notifications. Cable Insertion and Removal for data transfer. Media Player on/off.
- 3. Incoming and Outgoing Calls or SMS over the internet.(WhatsApp/Skype) Use of camera. Bluetooth file receive and send. Alarm notification. Push message from another app. Verify the behavior of the app on all the above scenarios. 6. LOW MEMORY Verify that application displays proper error messages when device memory is low and should exit properly. Application should not CRASH when device memory is low. Application performance when RAM is less and other apps are consuming it. 7. USER INTERFACE SCENARIOS Validation of buttons, text inputs, labels, etc. Validate each screen. Validate navigation flow. Validate app behaviour on device orientation. Validate app accommodate all sizes of text. 8. FUNCTIONALITY SCENARIOS Verification of offline/online functionality. Verification on Button clicks. Verify navigation between the screen is simple (user friendly). 9. LOW BATTERY Verify that when application is running and battery is low, proper message should be displayed to user. Application should not force exit unless it’s not a requirement. No abnormal behaviour of the application in case of low battery. 10. PERFORMANCE SCENARIOS Application should not crash/force close, when app is used uninterruptedly for a long time. Monitoring of device memory when app is being used uninterruptedly for a long time after regular intervals. Device should not get heated due to long use due to our app. 11. APPLICATION START/RESTART Verify application should launch successfully in defined timeline. Application is running in background, restart the app (test for different time interval 5mins, 15mins, 30mins, 1hr,.., 24hrs). Application should not crash. Behaviour should be as per requirement.
- 4. 12. EXIT APPLICATION Verify that user is able to exit application at any point of time with the help of Exit option. But it should be running in background. 13. KILL APPLICATION Verify that application can be killed and re launch successfully. 14. PUSH NOTIFICATION Verify that, if the application has a feature of providing Push Notifications, then it should be doing the same. In case of network failure during the processing of push notification, message should remain in queue for the specified time period as per the OS (IOS and Android) and message should be delivered whenever device is re-connected to network.