What is a mobile application testing strategy and why is it important? A mobile app is software designed to run on mobile devices such as a mobile phone or tablet instead of on a desktop computer. As we become increasingly reliant on our mobile phone, we depend more and more on apps that help with daily tasks – from tracking exercise programs to creating grocery lists to following the status of online orders. These apps, in turn, are becoming progressively complicated and why mobile application testing is so important.

The Importance of the Small Things

At Iterators, we have experience working on complex mobile apps and we understand why testing teams are essential for a positive user experience. Clients often think mobile app developers do the software testing instead of ISTQB-certified software testers. However, dedicated software testers are invaluable when creating mobile apps; they have the approach and knowledge to thoroughly examine each facet required.

In addition, software testing tends to have the smallest price point. So, this part of the mobile app testing process can be underestimated. Iterators’ software testers know how complex the testing can be and will provide enough detail to address any issues, or bugs, prior to launch.

In this case study, we will share how essential proper software testing is for a successful app to launch.

Client: Pharmaceutical Company

Our client is a pharmaceutical company with mobile apps for IOS and Android devices. This 2.0 version will track aspects of their treatment such as medication administration and lab results. We are suing IC Agile as part of our project management strategy.

The first thing to note is pharmaceutical companies are highly regulated, which always adds another level of complexity to the project. Second, we created test scenarios as the app must be extremely well-tested to ensure that software bugs will not affect its overall use. And third, the IOS and Android apps must be identical on both platforms for an industry so highly regulated.

Below is an overview of the areas that must be tested for the app to work effectively:

Introduction Screen, which was created to grab the user’s attention

• App to capture name, user’s email address and password which must be verified
• User must accept the Terms of Agreement and system must verify the Terms of Agreement
• Once accepted, the user will be able to move to the Login page

Login page

• User must be able to log into account
• Email address and password are required and this step must be verified before moving onto next step
• Link to Reset Password must be tested and successful before moving onto the Reset Password feature

Reset Password

• User must be able to reset the password
• User must receive email to confirm the password reset works
• Software testers must test the server to ensure settings are correct for email to be received by patient, without an error

Introduction of App

• User must see a welcome tour on the app, which only occurs the first time the app is opened. Therefore, as a software tester, we will set up many accounts to ensure that the welcome page does not show again when a user logs in again
• The user should be able to go through all the pages of the app, without interruption, and once complete, move on to the Homepage
• The client must determine how they want a user to access the screen (e.g., swipe from the left or right, hit another component to log your information, or both). As software testers, we have to test all options

Dashboard

• User should be able to see the Dashboard, which encourages them to explore the site
• The app should encourage users to track symptoms on the more than 10 screens that follow, including rash, fatigue, weight gain or weight loss, sleep disruptions, etc.

Reminder Tab

• User can go to Reminders and use the Reminder Tab, which allows user to sign up for reminders about taking the medication

Enter Symptoms

• User should be able to enter symptoms of the disease, such as rash, with ease. User can either touch the screen to indicate the areas affected or type in the symptom, and should note the severity of the symptom
• There is also a Help button in case a symptom is not displayed correctly and the user needs to report it

Enter Mood Symptoms

• User should be able to enter symptom for mood disturbances; mood only has a single value
• There is a tip on the Mood page as well as a Help button

Enter Sleep Symptoms

• User should log the quality of sleep. There is one value for sleep in contrast to multiple values for rashes.
• This data is sent to the server for analysis; therefore, the software tester must test the server to ensure the process works without a glitch

View Body Map History

• User can view how symptoms like the rash have progressed or decreased over different periods of time
• The calendar will allow you to change date ranges over a week, month, or year

Notes

• User can write notes to themselves, the pharmaceutical company, or their healthcare provider. Notes are created by using a drop-down menu and, in this case, only one note can be written on a given day, regardless of the category.
• The software testers verify that this functions correctly
• User should be able to view previous pages of notes, symptoms, or results from prior dates
• User sees a default date of “Today.” If the date is “Today,” future dates should be disabled
• User sees a default of “Today” and if the dates are prior dates, the app should not be disabled

Enter Lab Results

• User should be able to enter lab results on any day
• User should be able to receive Helpful Tips on the Enter Lab Results page
• The app is not connected to the patient’s doctor; the app is to help the patient keep track of their results in an easy way

In summary, what appears like a simple app for a mobile device is actually a complex program with numerous components. The above outline – though briefly touching upon the steps – illustrates the importance of mobile application testing for quality assurance.

Helpful Resources:

• Case Study: Example of Software Quality Assurance Testing
• Distinction Between Test Strategy and Test Plan