However, there are key points that we must consider whilst drafting out test plans and scripts for any mobile device. In this blog I attempt to cover some of the key points along with functional testing we should consider for mobile testing…
Unlike our desktops, mobile devices come with various interfaces, from small screens that can be re-orientated when the device is physically rotated, touchscreen only devices to those which allow a combination of touchscreen and hard keypads, soft keypad only and not forgetting the various navigation methods such as hard keys and trackballs.
Being familiar with the device you are/will be testing on is important, if you are not, ensure you have a play around with it before testing. Check for the following:
- Check for overall colour scheme/themes of the device. For example, Windows phone allow you to change the accent colour and background colours.
- Style and colour of icons
- Progress indicators when pages are loaded
- Menu’s – how they are invoked and typical items they contain
- Overall responsiveness of the application on the device
Screen Orientation/resolution: Applications should be tested in portrait and landscape view. Rotating the device fast, and checking to see the application’s response and errors
Touchscreens: Things to consider when testing touch screens are:
- Multi-touch such as : pinch to zoom and single touch.
- Long touch and short touch. For example, on some phones, pressing and holding an item will bring up a context menu, or a secondary function of a button.
Button Size & Position: Buttons and icons should be large enough to be seen clearly and be clickable by a fingertip.
Workflow: Use of radio buttons and checkboxes to minimize the amount of typing required, as this can be time consuming.
Factors such as interaction with other devices and interruptions from the devices own functions such as incoming phone calls should be considered.
Factors to consider are:
- Loss of Network Connections
- Memory Card usage
- 3G Network, 4G network, 2G network
- No SIM card in the device
- In airplane mode
Test intermittent network scenarios that a user might encounter in the real world such as:
Walk out of Wi-Fi range so the connection automatically switches to 3G/2G (for example, in a large building like a hospital or airport, or outdoors)
Ride in a lift or on a train where the network connection may go up and down
No network connection available at all
Device Options such as Screen Timeout/Auto on/off: Is your application subject to screen dimming or automatically turning off even when it is actually busy? For example, you wouldn’t want your screen to dim or turn off while watching a slideshow of your photos.
Screen orientation: You may be able to enable/disable automatic orientation switches when the device is rotated. Does your application apply the setting set on the device?
Font: Does choosing a different font family, size, or style affect the appearance and usability of your application?
Connections: Using one of the connections on a device, such as Bluetooth or Microsoft Direct Push (only on Windows Phone devices), could have adverse effects on your application. How does enabling/disabling Bluetooth or other connection types affect your applications behaviour?
Can be a great way to achieve testing coverage across multiple devices, but it is not safe to assume that just because your application works on an emulator, it will work on the actual device itself. When using Emulators, it is important to consider the following points:
- Not all activities can be realistically emulated, like switching network connections, or taking a picture or video.
- Some activities don’t work at all on emulators, like streaming video on a Blackberry emulator.
- Due to lower device power and memory, the application could exhibit slower performance overall when run on an actual device (versus in an emulator on your powerful desktop computer).
- If the emulator and actual device have different resolutions, your screens may not display as you expect.
Mobile device applications have much less memory and power available than PC’s
This applies to applications which require sensitive data storage such as banking applications, and how the application behaves under various device permission schemes.
Mobile devices will no doubt continue to grow, and as testers we will need to keep up to date with the latest gadgets out there to keep on top of the latest changes in OS and functions belonging to a gadget. No doubt the device functions discussed in this blog will continue to grow.