Mobile App Quality Assurance Testing

What is Mobile App Quality Assurance Testing?

Quality assurance testing is to ensure that the  app operates at top-quality giving users a glitch-free experience. Quality assurance testing includes functional, usability, performance and security testing.

What is is Usability Testing?

Usability testing is to make sure that the app is intuitive, easy-to-navigate and comfortable in users hands for ultimate satisfaction of the customer.

1. Identified Types of Testing – It is a requirement that the application has to work in all iOS and most Android devices  after  Android Jelly Beans as the end consumers can have diverse devices. To ensure that the app worked in all the devices we selected  combination of manual testing, automation testing and testing in cloud simulators are used.

2. Perform Manual and Automated Testing –The development process followed for  any project is SCRUM and each sprint is two weeks long. Every two weeks the app development team delivers a viably completed product to the QA team and QA would run their unit test cases on the build. QA has to ensure that previously completed items still work.  JIRA and other online bug trackers are used to file and track defects.

3. Providing 24/7  QA Support – We follow a SCRUM development model (QA team is integral part of the development team throughout the project).  This ensures timely and steady progress in the app  development.

4. Beta Testing – After this initial setup, once the particular build was deemed a Minimally Viable product Beta testing is done using the beta users from online beta testing websites. This ensures that almost every bug is fixed before the app is released with all necessary features and functionality. Beta testing facility in Google play store and app store help.

5. Performance Functionality Testing – The functionality, performance (stability, responsiveness, resource usage, stability parameters as per standards) and user interface for the delivered build is thoroughly tested.

6. Device Testing – The app is tested across multiple OS versions/devices using the cloud simulation tools and is also physically tested in our small mobile application testing lab

7. Maintained Test Case Sheet –During the whole process the QA team maintains the test case sheet and at last certify the app build to release. The entire end-to-end mobile application testing process takes a real team effort.

8. Generated Test Summary Report – Finally QA manager generates the test summary report. This is a management report which provides details of any important information uncovered by the tests conducted, includes assessments of the quality of the testing effort, the quality of the software system under test and statistics derived from incident reports. The report also records different types of testing performed.  This final document indicates whether the software system the mobile app  under test is fit for use and has met acceptance criteria defined as such at start by the app owner.

Modules Test Case Description Expected Result
1.Installation Verify that application can be Installed Successfully Application should be able to install successfully.
2.Uninstallation Verify that application can be uninstalled successfully User should be able to uninstall the application successfully
3.Network Test Verify the behavior of application Cases when there is Network problem and user is performing operations for data call. User should get proper error message like “Network error. Please try after some time”
4.When network is back Verify that user is able to establish data call when Network is back in action. User should be able to establish data call when Network is back in action.
5.Voice Call Handling (Voice Accept) Verify that user can accept Voice call at the time when application is running and can resume back in application from the same point. User should be able to accept Voice call at the time when application is running and can resume back in application from the same point.
6.(Call Rejection) Verify that user can reject the
voice call at the time when
application is running and can
resume back in application
from the same point.
User should be able to reject the Voice call at the time when application is running and can
resume back in application
from the same point.
7.Call Establish Verify that user can establish
a Voice call in case when
application data call is
running in background.
User should be able to establish
a Voice call in case when
application data call is running
in background.
8.SMS Handling Verify that user can get SMS
alert when application is
running.
User should be able to get
SMS alert when application
is running.
9.Resume Verify that user can resume
back from the same point
after reading the SMS.
User should be able to resume
back from the same point after
reading the SMS.
10.Unmapped key Verify that unmapped keys are
not working on any screen of
application.
Unmapped keys should not work
on any screen of application.
11.Application logo Verify that application logo with
Application Name is present ,
application manager and user
can select it.
Application logo with Application
name should be present in in
application manager and user
can select it.
12.Splash Verify that when user selects
application logo
splash image displayed.
When user selects application
logo in application manager
splash should be displayed.
13.Time Note that Splash do not remain
for more than 4 seconds.
Splash should not remain for fore
than 4 seconds, as in manifest.
14.Low Memory Verify that application displays
proper error message when
device memory is low and exits
gracefully from the situation.
Application should display
proper error message when
device memory is low and
exits gracefully from the
situation.
15.Clear Key Verify that clear key shouldnavigate the user to previous
screen.
Clear key should navigatethe user to previous screen.
16.End Key Verify that End Key shouldnavigate the user to native
OEM screen.
End Key should navigate theuser to native OEM screen.
17.Visual Feadback Verify that there is visual
feedback when response
to any action takes more
than 3 seconds.
There should be visual feedback
given when response time for
any action is more than
3 second.
18.Exit application Verify that user is able to
exit from application with every
form of exit modes like Flap,
Slider,End Key or Exit option in
application and from any point.
User should be able to exit with
every form of exit modes like
Flap,Slider,End Key or Exit
option in application and from
any point.
19 .Charger Effect Verify that when application
is running then inserting and
removing charger do not cause
any problem and proper
message is displayed when
charger is inserted in device.
When application is running the
inserting and removing charger
should not cause any problem
and proper message should be
displayed when charger is
inserted in device.
20.Low Battery Verify that when application is
running and battery is low then
proper message is displayed
to the user.
When application is running and
battery is low then proper
message is displayed to the
user telling user that battery is low.
21.Removal of Battery Verify that removal of battery
at the time of application data
call is going on do not cause
interruption and data call is
completed after battery is
inserted back in the device.
Removal of battery at the time of
application data call is going on
should not cause interruption and
data call should be completed
after battery is inserted back
in the device.
22.Battery Consumption Verify that application does
not consume battery
excessively.
The application should not
consume battery excessively.
23.Application Start/Restart 1. Find the application icon and
select it
Application must not take
more than 25s to start.
24.Application Side Effects Make sure that your application
is not causing other
applications of device .
to hamper
Installed application
should not cause other
applications of device
to hamper.

Augmented reality

    Download now Jewelry AR mobile app     

                    Call us for mobile enterprise applications. |  So you need Cross platform mobile development?

Leave a Reply