A Mobile Phone, more frequently known as cell phone, is a device that can make or receive telephone calls over radio link.
Let's take a look at different types of testing that should be considered for smartphones.
Installation Testing: Test that the application can be installed & uninstalled successfully.
Functionality Testing: Test that the application is functioning according to the design. The application should be performing actions that it is intended to perform.
Widget Testing: Test by adding, deleting & using widgets & ensure it is working as per its functionality. For e.g: a music widget should play music. Note: this testing is not applicable for Apple devices.
Phone Interrupt testing: Test the application behavior on phone call, message or any other notification.
Stress Testing (monkey test for android): There is a command in android where it generates series of events at different frequencies. Make sure the app passes this test. The command used for gererating event is:
Click here to learn more about this type of testing
UI Testing: Test to ensure the UI of the application is good for mobile devices of different resolutions.
Compatibility Testing: A compatibility test should be done on as many devices as possible. Typically, a developer performs unit tests on emulators. Tester should perform tests on target devices.
Performance testing: check memory leaks,
Although, it may not always be possible to test all applications on all different devices. However, as much as possible, testing should be done on actual devices because of the following reasons.
Resource Availability:
Simulators may have access to more or less resources, depending upon the system it is running.
Program Performance:
Simulator may run at a different speed than the actual device.
Communications Availability:
If app communicates over bluetooth/WAN, simulators tend to simulate in such a way that these communication channels are always available & work. On the other hand, in the real world there can be outages & slowness of these channels. So, the application under test may not be tested for such scenarios using simulators.
Hardware Exceptions:
It is not possible to test how does the code handles low battery, power-offs, insufficient memory etc.
Some of the UI elements also look different in simulators & emulators.
Issues with Different Simulators
1. Blackberry Simulator
Tools
We have developed an online simulator that can be used to test websites in most of the devices.
Click here to access the tool.
Subscribe to Quality Assurance Knowledge Base! by Email
Let's take a look at different types of testing that should be considered for smartphones.
Installation Testing: Test that the application can be installed & uninstalled successfully.
Functionality Testing: Test that the application is functioning according to the design. The application should be performing actions that it is intended to perform.
Widget Testing: Test by adding, deleting & using widgets & ensure it is working as per its functionality. For e.g: a music widget should play music. Note: this testing is not applicable for Apple devices.
Phone Interrupt testing: Test the application behavior on phone call, message or any other notification.
Stress Testing (monkey test for android): There is a command in android where it generates series of events at different frequencies. Make sure the app passes this test. The command used for gererating event is:
$ adb shell monkey [options] <event-count>
Click here to learn more about this type of testing
UI Testing: Test to ensure the UI of the application is good for mobile devices of different resolutions.
Compatibility Testing: A compatibility test should be done on as many devices as possible. Typically, a developer performs unit tests on emulators. Tester should perform tests on target devices.
Performance testing: check memory leaks,
Although, it may not always be possible to test all applications on all different devices. However, as much as possible, testing should be done on actual devices because of the following reasons.
Resource Availability:
Simulators may have access to more or less resources, depending upon the system it is running.
Program Performance:
Simulator may run at a different speed than the actual device.
Communications Availability:
If app communicates over bluetooth/WAN, simulators tend to simulate in such a way that these communication channels are always available & work. On the other hand, in the real world there can be outages & slowness of these channels. So, the application under test may not be tested for such scenarios using simulators.
Hardware Exceptions:
It is not possible to test how does the code handles low battery, power-offs, insufficient memory etc.
Some of the UI elements also look different in simulators & emulators.
Issues with Different Simulators
1. Blackberry Simulator
- Blackberry simulator is extremely slow
- Mouse does not work
- Crashes a lot
- Sometimes it gets impossible to close the application
2. Android Simulator
- Although faster, it's small screen on the phone makes it tedious to test the entire application.
- Zoom-in is not possible in modal window
- In original Zoomed out size, it gets difficult to see a specific feature.
3. Ipad & Iphone Simulator
- Slow
Tools
We have developed an online simulator that can be used to test websites in most of the devices.
Click here to access the tool.
Subscribe to Quality Assurance Knowledge Base! by Email
No comments :
Post a Comment