Posted by:Ranjit Anand May 13th, 2014

Does the testing phase of your mobile app project take longer than estimated ? Ever discovered that your app needs more types of testing other than just functional testing?

The QA phase in a project is arguably given lesser importance at the start of the project than it deserves. Like any other entity, you start seeing its impact only towards the end of the project. The right way out is to consider the potential of comprehensive app testing right at the start of the implementation. Here are 5 important factors to consider while testing your app.


This goes without saying. Functional testing is the most commonly considered type of testing for any app. At the start of your project, get your team to write up test cases revolving around all the functionality of the app. Starting test case documentation early in the project helps with improved understanding of the requirement and also helps in unearthing certain scenarios which otherwise would be ignored during the requirement gathering phase.


Make sure everyone in the project understands the difference between ‘User Interface’ and ‘User Experience’. Finding visual element bugs is User Interface related. However, in addition, testers need to understand the User Experience from various points of view such as user demographics, animation, touch and gestures used, contextual implementation of functionality, etc. So considering usability testing of the app prior to starting the project is absolutely vital.


As more and more apps are released on the app store, some of the more unusual factors prove to be key to the success of an app. One such key factor is the performance of the app. Given the attention span of the audience, the faster the response of the app the better. Performance optimization has to be considered during the implementation of the app in terms of optimizing the web service communication, local caching, media streaming optimization, etc.

Battery Drain & Location services

I have come across many smartphone users deleting apps from their phones just because the app consumed more battery than other apps. So sufficient steps have to be taken during the technical design to avoid excess battery consumption. When the app requires location services, it is very important to double check that the app is not running the location services in the background. This results in battery drain. Web server calls have to be made only when required and CPU and memory usage has to be optimized especially when the app is required to run in the background.


Many consumer based apps require rigorous testing as the behavior of each consumer varies from one scenario to the next. Besides manual testing, there are certain scenarios which can’t be executed during manual testing, but which can be automated by scripting the test cases. This will ensure that certain user interactions are tested completely. Stress testing can be performed using test scripts.

What are the steps that you consider before mobile app testing? Any additions to the list ? Share your thoughts !

Take charge of your enterprise app strategy ! Download this eBook with the 10 best practices and get started

Leave a Reply

Your email address will not be published. Required fields are marked *