There is huge growth in mobile devices, the number of apps and, not coincidentally, the number of mobile apps That need testing.
With problems like device fragmentation and varying orientation, there is a lot That Can go wrong with the mobile app. If you are new to testing mobile apps, here are some things to do before testing the app and some important things to check while testing the app.
This helps reduces the invalid bug count later in. the test cycle.
In particularly, Check That the Desired version of the mobile OS is running and know Whether the device is 3G or 4G.
Some important mobile settings include:
As nice as it is to catch bugs in Situations like this, you're going to need to know how to unlock the phone to continue testing.
The UI Should be checked by changing the mode while the pop-up or message box is appearing on screen Reviews inside the app.
One issue That I found recently Involved just such to bug on the login page of an app. Changing portrait to landscape while typing in to the username field Resulted in the app displaying just a greyed out background and not username or password fields.
This is a major defect, but other user interface elements like the size of the text fields, buttons and images Should all be checked to Ensure They are properly sized and adjusted When the mode changes.
For example, removing to mobile agent from the mobile agent id configuration parameter Should cause application to stop working On That device.
On Android devices, there is a UI issue related to the password text field. If you tap on the username text field on the login page of any application then notice That There is No Border on the text field. But When do the same on to password field then to border Appears around the text field.
If you are new to testing Android, This Will look like a defect, but really it is a property of the default browser on Android OS.
With problems like device fragmentation and varying orientation, there is a lot That Can go wrong with the mobile app. If you are new to testing mobile apps, here are some things to do before testing the app and some important things to check while testing the app.
Before Starting
Know the Apps Limitations
Before start starting testing it is useful to speak With The developers. And learn about any Known faults and Limitations like problems with scalability and response time.This helps reduces the invalid bug count later in. the test cycle.
Be comfortable With The device
Before start starting testing, the tester Should Have to feel for the device and know how Apps are supposed to work and feel. This will help spot Both user interface and performance issues.Check the Mobile Device Hardware and Software
Check That the hardware and software of the mobile device on Which testing is to be donate meets the Requirements and design specifications.In particularly, Check That the Desired version of the mobile OS is running and know Whether the device is 3G or 4G.
Manage device settings:
A tester must have sound knowledge of the various settings available on the mobile device and how to change them.Some important mobile settings include:
- Phone settings: Network settings, Wi-Fi settings, remember my password option, GPS toggle, zoom page option, Wi-Fi sleep and screen lock.
- Browser cache: how it is saved, how can it be cleared and other dating saved in the device.
- Browser settings: how to create and save bookmarks, how to clear cookies and other cookie settings.
As nice as it is to catch bugs in Situations like this, you're going to need to know how to unlock the phone to continue testing.
GUI test cases
While creating test cases equal emphasis Should be Given For writing UI test cases ace it is the look and feel of application Which makes it a success.While Testing
Style Guides
The Implementation of to style guide Provides uniformity in style and PM formatting. During testing, style guides Must Be checked FAQ frequently to ECOG to consistent UI. It helps in checking for the placement and style of elements like message boxes, pop-ups and text.Testing with Both the modes:
Testing on mobile devices Should be donate in Both portrait and landscape mode. Many times issues crop up due to change Average in the mode while typing in to text field or moving from one page to Reviews another Reviews inside the app.The UI Should be checked by changing the mode while the pop-up or message box is appearing on screen Reviews inside the app.
One issue That I found recently Involved just such to bug on the login page of an app. Changing portrait to landscape while typing in to the username field Resulted in the app displaying just a greyed out background and not username or password fields.
This is a major defect, but other user interface elements like the size of the text fields, buttons and images Should all be checked to Ensure They are properly sized and adjusted When the mode changes.
Localization:
Localization can be tested in two ways:- Localization Within the application Which can be donate through the functional requirements.
- Localization by setting the mobile device language. In this case all of the options, UI, responses in the app Should be tested thoroughly.
Configuration File
If the server is localmente available then configuration file of the app can be tested by the tester. There are many parameters Reviews inside the configuration file Which can be altered and then can be verified in the app.For example, removing to mobile agent from the mobile agent id configuration parameter Should cause application to stop working On That device.
Secure and Non-Secure Ports:
If required, la aplicación Should be tested Both on non-secure (http://) and secure (https://) ports. The certificates Should be Recognized and proper security You messages Should appear.Effect of Keypad:
Touch and keypad Should be used while testing on specific mobile devices (Blackberry). Touch keypads can cover up application buttons and UI elements.Effect device buttons:
The effect of the device buttons Should be tested thoroughly. Check Whether the Back button logs out the user, or refreshes the page, or is disabled. Check Whether the Go button logs in the user without tapping on login button. Check Whether the Close button is working ace is Intended. Check Whether the refresh button is working According To the requirements.Device specific issues:
Some issues appearing on an app May be device specific.On Android devices, there is a UI issue related to the password text field. If you tap on the username text field on the login page of any application then notice That There is No Border on the text field. But When do the same on to password field then to border Appears around the text field.
If you are new to testing Android, This Will look like a defect, but really it is a property of the default browser on Android OS.
Other factors:
Other things to watch for include:- Session time out period: Check That the session times out properly When a device is left untouched for proper time. Check That the user is logged out, That the app is closed and That the dating does keep refreshing.
- Memory / CPU Utilization: Check That the app does not overuse the CPU or memory space. Make sure the app can not use more resources than are Allocated.
- App Logs: These Should be Referred to debug issues.
Comments
Post a Comment