Determining The Goal Of Mobile App Testing

Goal of Mobile App Testing

Goal of Mobile App Testing

Often when testing starts on a mobile app testing project, it is without thought as to the goal of the testing. This can result in wasted time by the testers involved and something much worse; inadequate testing for the mobile app.

In the field of mobile app testing for example, there are several possible goals. The goal of any testing should be derived from the person or company who is requesting it. These are the people who are effectively paying for the testing to be completed and so this is a key factor in determining the goal.

The mobile app tester should take on board the requirements or instructions for the testing. They should analyze these and determine if the proposed testing will be sufficient to satisfy them. During this analysis phase, questions can and should be asked by the tester in order to determine the goal. If the tester does not feel that the proposed testing will be sufficient, then they should highlight this fact immediately and propose alternative methods to achieve the intended goal.

As an example, let’s say a mobile app is developed by a company, they ask you to test it for them. They have given you no explicit instruction, they just want it tested. Now, in order to test the mobile app effectively you need to ask some questions to form your testing goal. The following are some standard questions to help you achieve this:

Which devices do you want the app tested on?

What do you consider to be high risk areas of functionality?

How much of the apps functionality has been already tested?

Who is the intended audience of the app?

Is this a new app, or an updated to an existing app?

From the answers to these types of questions you can quickly determine your goal. For example, if the requirement is to just test the app on an iPhone 4S, then the obvious question you need to ask is; why? Has the app already been tested on other iOS devices? So, perhaps with further questioning the goal here may be a compatibility test on different device models.

If the app has already been widely tested, then the goal here may be to perform a sanity test prior to its actual launch.

If the developer states that they are not confident with specific functionality of the app, then this is an area that should take most of the focus of your testing. Lack of confidence from the developer should also trigger in your mind that significant testing is required throughout the app, and not just on the areas of concern.

If this is an update to an existing app, ensure you are aware of what has been changed from the previous version. One good thing to do is view the user’s comments on iTunes or Android market for the previous version. This gives you key insight of what previous problems existed and what is hopefully fixed in the new version, along with key insight into the usability aspects of the app itself.

Attempt to make your own list of questions. The key here is to make questions that will trigger something in your mind that will help you determine the goal of the testing.