• info@helpingtesters.com
  • helpingtesters

Mobile Application Testing Process

January 28, 2018 Beginners Mobile Testing
Mobile Application Testing Process

Mobile Application usage trend has been widely spread across almost all the business lanes – Consumers, Enterprises, Publishers, Retailers, Financial Service Providers, Pharmaceuticals, Automobile Dealers, Healthcare Providers, Schools, Universities – are to just name the few. The ever-growing demand for mobile applications has made the decision makers focus on designing strong mobile strategies and testing it before it reaches the target users. Just building the application with all the needed features and functionalities is not sufficient; testing the mobile application rigorously is critical before releasing it to the market, and has its own process – Mobile Application Testing Process.

Mobile Application Testing Process also has its own set of procedures to be followed, this can again be tweaked as per project requirements. Strong mobile testing strategy and planning will lead to the success of its entire testing process and enhances quality. Going forward with this article, we will see the general testing process defined for Mobile Applications.

Mobile Application Testing Process – A Step-by-Step Approach

⇒ Preparatory Phase

This is the phase which occurs once the development phase is almost complete. Activities that are carried out in this phase are listed as below:

  • Decide the target devices on which the mobile application has to be tested
  • Analyze functional requirements
  • Check and list the requirements:
    • Does the app interact with other apps?
    • Are all the features functional?
    • Is the app Native or Mobile-web or Hybrid?
    • Is the app testing limited to front-end? Does it include back-end testing as well?
    • What is the compatibility with multiple networks?
    • How frequently data/space based on usage?
    • How is the load handled?
    • Does any change in phone status affects the flow of application?
  • Have the testing team ready (onsite and offshore)

Identify Testing Types

This is the phase to identify the different types of testing to be carried out for the app – Functional, Usability, Compatibility, Performance, Beta, etc – on the identified devices. Also, it is equally important to select the combination of manual testing, automation testing, and testing in the mobile cloud, due to wide-diversity of the devices and platforms.

Test Case / Script Design

Prepare test case document for each and every feature and functionality (as and when they pitch in). Prepare the automated test scripts for basic functionalities which are expected to be stable and not to be changed frequently. Along with basic functionalities, if required, prepare automated test scripts for new / modified features as well.

In addition to functional test cases, few special cases should also be focused to cover:

  • Battery usage: To keep track of battery usage while running the application, to observe application behavior at low battery power
  • Speed of application: to test application responsiveness with different network states, different memory usage patterns, on different devices
  • Data requirements: to verify download and installation when there are different data limits – limited, moderate, high – at all the limits user should be able to download and install the application
  • Memory requirement: to download, install, use the application, uninstall, re-install

Prepare separate suites for manual test cases and automated test scripts as required by test cycles.

Test Environment Setup

Establish the testing environment by downloading, installing, and configuring the application on testing devices. Ensure that the test version of the application is setup before starting the actual testing.

Manual and Automation Testing

In this phase, the identified testing team will execute both manual test cases and automated test scripts suites on major devices/simulators/emulators. For every new build, along with manual test cases and automated test scripts for new / modified feature, run the automated test scripts for basic functionalities to ensure that there is no breakage.

Log the defects found in the defect management tool and follow its life cycle as intended in the project.

Usability Testing / Beta Testing

Once the application is tested by testing team, release the beta version of the application to market. Announce the beta version of the application, so that beta testers can start the usability testing to identify functional, usability, navigational, and content issues.

This phase requires maintaining cross-platform matrix to ensure the platform coverage achieved by beta testers.

Performance Testing

Responsiveness, scalability, resource usage, and stability of the application is tested for the standards.

Security and Compliance Testing

Ensure that the application is secure by validating SQL injection, data dumps, session hijacking, packet sniffing, SSL, and intruders.

Device Testing

Execute test cases and test scripts in all the identified devices through the cloud or in all the devices available in the lab. Ensure that the good test coverage is achieved in terms of multiple devices / multiple OS / multiple versions of OS.

Test Summary Report

Generate the test summary report providing the details of

  • Important information uncovered by the tests conducted
  • Quality of testing effort
  • Quality of the mobile application
  • Statistics derived from incident reports
  • Different types of testing performed, and time taken for each of them

This report should also indicate:

  • Whether the mobile application is fit for use
  • Does it meet all the acceptance criteria?
  • Can it be released to the market

Strictly following the Mobile Application Testing Process leads to the success of its launch to the market.

About the author

Nandini KS editor

Hello, this is Nandini.

Leave a Reply

Your email address will not be published.