Testing of Mobile Applications
Every software tester has to make a choice about the mix of different techniques and methods he/she will use during testing. Each testing choice will have pros and cons associated with it, and one will probably find that any testing choice will be completely satisfying.
The developers of software for mobile phones based on Windows Mobile, classify the mobile application tests to the following types:
- Sanity test
- Feature Test
- Defect Verification
- Regression Test
- Hopper Test
Rapid-testing of features to check the basic features and stability. Testing basically boils down to finding "fall / not fall" and if there are no rough errors.
Testing of all the features possibilities on the basis of Test Suite document, which in turn, is created on the base of specifications for the feature.
Checking of some software bugs that were identified during Feature Test.
Repeated Feature Test of features that used to work, but were broken in some build. We have to verify not only the features, but all related to it.
Testing of features or the entire platform based on Windows Mobile. This is a stress test for stability. Microsoft has significant requirements for each feature, which can be included in next build. If within 25 hours feature is not "drops" the phone under the influence of Hopper application, that means feature is stable.
This is tool, which randomly generates a Windows event and sends it to all windows it can reach to. Thus it with breakneck speed sends in all windows such events as "pressing buttons" "mouse", "closing window" etc. As a result, if your application has a memory leak or some kind of instability - it will not survive for 25 hours.
There is also integration testing, when all features are collected in a single build and check the efficiency of "assembly".