Mobile Testing : Guide to Functional testing in Mobile App
Some or all of the following testing types may be performed depending on your mobile testing requirements
1.Functional testing
2.Performance testing
3.Security testing
4.Usability testing
5.Compatibility testing
6.Recoverability Testing
Functional testing
The functional testing of Mobiles normally consists in the areas of testing user interactions as well as testing the transactions. The various factors which are relevant in functional testing are
1.Type of application based upon the business functionality usages (banking, gaming, social or business)
2.Target audience type (consumer, enterprise, education)
3.Distribution channel which is used to spread the application (e.g. Apple App Store, Google play, direct distribution)
The most fundamental test scenarios in the functional testing can be considered as :
1.To validate whether all the required mandatory fields are working as required.
2.To validate that the mandatory fields are displayed in the screen in a distinctive way than the non-mandatory fields.
3.To validate whether the application works as per as requirement whenever the application starts/stops.
4.To validate whether the application goes into minimized mode whenever there is an incoming phone call. In order to validate the same we need to use a second phone, to call the device.
5.To validate whether the phone is able to store, process and receive SMS whenever the app is running. In order to validate the same we need to use a second phone to send sms to the device which is being tested and where the application under test is currently running.
6.To validate that the device is able to perform required multitasking requirements whenever it is necessary to do so.
7.To validate that the application allows necessary social network options such as sharing, posting and navigation etc.
8.To validate that the application supports any payment gateway transaction such as Visa, Mastercard, Paypal etc as required by the application.
9.To validate that the page scrolling scenarios are being enabled in the application as necessary.
10.To validate that the navigation between relevant modules in the application are as per the requirement.
11.To validate that the truncation errors are absolutely to an affordable limit.
12.To validate that the user receives an appropriate error message like “Network error. Please try after some time” whenever there is any network error.
13.To validate that the installed application enables other applications to perform satisfactorily, and it does not eat into the memory of the other applications.
14.To validate that the application resumes at the last operation in case of a hard reboot or system crash.
15.To validate whether the installation of the application can be done smoothly provided the user has the necessary resources and it does not lead to any significant errors.
16.To validate that the application performs auto start facility according to the requirements.
17.To validate whether the application performs according to the requirement in all versions of Mobile that is 2g, 3g and 4g.
18.To perform regression testing to uncover new software bugs in existing areas of a system after changes have been made to them. Also rerun previously performed tests to determine that the program behavior has not changed due to the changes.
19.To validate whether the application provides an available user guide for those who are not familiar to the app
Post a Comment
Post a Comment