Date:________ Mobile App Testing Checklist - Tester name____________

Done Y/N or Issues Screen Shot Reported / Retested after

SN Module Checkpoint Completed
N/A Found taken Date issue fixed

1 UI/UX Font styles - Font size, color, and family.

Check the CSS properties of an element.
Check if the images are not breaking and don’t have any watermarks.
Check if elements are not breaking or distorted on different browsers and screen resolutions.
Check if the label text is readable.
Check if the error and validation messages are displaying correctly.
Check if there are no spelling mistakes in the field labels and web page headings.
Check if the disabled fields are not accepting any input.
Check if the links are visible and distinguishable from the other text.
Check if the social networking icons are rightly placed on sites.
Check if there are no broken links on the web page.
Check if there are no unnecessary blank spaces between the elements on the web page.
Check if the horizontal and vertical scrollbars are appearing wherever necessary.
Check if the site logo is visible and clickable.
Check if the web elements are not overlapping anywhere on the web page.
Check if banner images or any other large images are not exceeding the screen limit.
Check if the Privacy policy links are readable and clickable.
Check if the Cookie policy section is visible with buttons and contents.
Verify if elements in the dropdown are not overlapping.
Check if the menu or submenu that is selected remains highlighted.
If there are any country fields or phone number fields, check if the country codes are displayed correctly.
Check
If thereifare
theany
autofill
mapsfunction is working
on the site, check ifastheexpected
user canand thatinthere
zoom and are no out
zoom UI issues.
the map without any UI
distortion. Check if the user can see the locations on maps.
For
Whereanyever
reports or charts
loader checkonly
is required if the
thefigures areshould
spinner displayed accurately.
not be there, there should be a valid message along with
2 Loader the spinner. Ex-loading user Data.
The standard
In case Loading
the screen takestime
overfor any screen
5 seconds shouldthe
to show bepage
3 to or
5 seconds.
result, it ought to contain a progress bar so the user
comprehends the process is proceeding.
Due to any error if the application fails to load the required data then shows an appropriate error message also
there
In theshould be a should
input field Retry button.
show the cursor and on it, tap keyboard should be opened, accordingly numeric,
3 Input Box alphabetic, etc.
If an input Text field is Numeric then the Numeric keypad should be by default open.
In the input text field is text field then it should open the alphanumeric keyboard.
If the User tap on the search text field then the keyboard should have a Search Button.
When the user taps on the email address field then the keypad @ should come in that keypad.
Every text field
If an input should
text field is abedate
truncated
then use with ellipses
standard if it crosses
calendar view the
( formaximum visible
iOS/Android) limit be there. The date
should
format
Whenever should be the
the user same asany
received defined.
OTP, it should auto-populate on the suggestion field of the Keyboard,
4 OTP Keyboard should open with the numeric keypad.
OTP should be generated within the time period.
Limitations of number of OTP generation for single authentication.
It is received only on registered Mobile Number / Email Address.
Network delay for expiry of One-Time Password.
 Verify that once expired, it should not be used for any authentication.
Verify that once used, it should not be allowed to use again.
Verify that once the user resent the OTP, the old one should be of no use.
Permission Only use the permissions necessary for your app to work. Ex: if permission is required to use a camera then
5
Access pop up only the camera
For every access,should
you needbe mentioned.
the developer Generic, messages
must provide shouldusage
a proper not bedescription.
shown be there.
- a common reason for the
app rejection if a proper description not mention.
If an application has language selection then a permission pop-up should come after the selection screen.
When the map screen is opened the map should be appropriately zoomed in i.e. the area where the location/s
6 Map On
are selecting of location
present should from there
be visible, a map, the location
should not be ashould getthe
need for an update
user to on the moving
manually zoompin.into the map to see the
area.
In the map
Should screen pickup
be displayed location
to enable and drop-down
the location service location/s
popup while must
thebelocation
markedservice
with different
is off andcolors.
the user opens
the map screen.
Alerts / In app
7 Pop-ups should have
Check password shoulda very clear text8 like
be between to 15"Login successful"
characters rather than
and password only
should "Success".
contain at least one numeric digit
messages.
and a special character & upper case letter , if any validation failed then there should be a proper error
In case an item is added to the card "Item added to cart" rather than only added.
message.
8 Password The password should always display in encoded format.
Password hint should be there.
9 Notification Notification should be received even if the app is closed.
Notification should be received even if the device is locked.
Notification should be received even if a user is receiving another application.
Notification received in multiple time zones.
Notification should be clickable and on click, it should redirect the user to the particular page.
Check sound, vibration & blinking.
Account information-related Notification should not received by a user when the user is not Logged in.
Notification
If the user is should get removed
on the home page andfromusernotification bardevice's
clicks on the once theback
notification is opened.
button (in the case of the Android app)
then there should be a pop-up with.
Verify when the notification comes in the foreground, then the notification will display directly on the app
(App in foreground).
Recent notification messages always should be on the top of a stack.
Verify to prevent repeating the same notification over and over again by the possible triggers.
If permission is Off for the push notification then it should not be received in the notification bar
For new users, Previous admin notifications should not be listed
10 Search The search results displayed should be relevant to search keyword
% sign-in search keyword should not redirect to 404 ERROR
The application should not crash if the user inserted % in the search field.
When should
There the userbestarts typing asearch
pre-defined word in the text
criteria forbox it should suggest
auto-complete words
e.g. after that the
typing match
firstthe typed it
3 letters keyword.
should
suggest a matching keyword.
When user clicks on any link from result and navigates back, then result should be maintainedWhen a user
clicks on any link
After clicking fromfield
Search the -result
searchand navigates
history back,
should the result (latest
be displayed shouldsearch
be maintained.
keyword)After clicking the
Search field - search history should be displayed (latest search keyword)
All search keyword/filters should get cleared on clicking Reset button.
Search results should be cleared on clicking clear search button.
History displayed in the search field should be relevant to login user only.
Pagination should be tested for searches returning a high number of records.
The total number of search records/results should be displayed on a page.
Search keywords should get highlighted with color in the search results.
For eCommerce sites - search keywords should suggest similar kinds of products/items.
For Advanced Search - limited search filters should be provided.
Water text should be provided for user to understand what to search.
 Validate search rules defined for “Exact Match” with the search keyword.
Validate search rules defined for “Similar Match” with the search keyword.
Validate search rules defined to search with a set of keywords
User
After should
logout be able clicks
if user to search whenbutton
on back he enters
userthe keyword
should and
not be hitstothe
able ‘Enter’
login withinbutton
sameon keyboard.
session, it should
11 Session redirect to login page.
If user logged in on multiple devices and Logout from one device then it should Logout from all
platform/devices.
Maximum Session out time should be set for Secured website.
12 Browser If Browser cookies are cleared and user tries to login, the system should ask for credentials again.
‘Remember Form Data’ setting of the browser should not remember the password.
Validate the login functionality when browser cookies are turned OFF.
13 Security When logged in user copy URL and paste in new browser window, it should redirect to Login page.
Users should not be allowed to copy and paste Password from the text box.
Notification email for multiple device login - if the user login from an unusual device/machine.
Entering
After 3 orLogin credentialsattempts
5 unsuccessful using virtual keyboard
of login, should
user login be provided
credentials for get
should banking
locked application.
for a specific period e.g.
24 hours
SSL certificate should be implemented/installed for Secured Website.
One added test scenario needed to be taken into account is the performance of features may vary from one
Two-way authentication
carrier to the through
other. So, check howOTP
the on mobile/email
application shouldatbealltested
is working for banking
the devices of theapplication.
2G, 3G, 4G & Wifi
14 Network networks.
Verify error messages, for instance, “Network Error” if there is an occurrence of an inaccurate network error.
Check how the application behaves when connectivity is failed or suddenly switches from 4G to 2G.
Verify the error message we are showing when the user launching the application in case of No network.
Back
15
Navigation In Android device has a back navigation button so no needs to implement a back button in-app.
In iOS, there is no in build back navigation button so the back navigation button should be there in-app.
16 Links Test all internal links are navigating within application as per requirement
Test links jumping on the same pages.
Test to check if there are any blank pages to link.
Test Links opening in another tab /windows as per requirement.
Compatibility Testing for all links on other browsers.
Check loading time for internal links as per requirement.
Check whether shared link is getting shared properly with correct address.

17 Live Tracking Position of the car should be in route direction.

Car
The should
positionbeofmoved
the carwhen driver
should be onis the
movedroadinwhile
routemoving,
directionand should not be over the other object like a
building, beside the road.
Route lines need to be erased when a car is moving further in the route direction.
Route line must be re draw if the driver changes the route.
Driver and user location must be the same in the tracking screen.
The
The location
location must
must be
be updated
updated when opening
after any theinterruption
type of application while
from the background.
using the application. like a phone call,
messages, open other application.
Carcarshould
A shouldnot
bebe stuck when
moving driver
smoothly in makes a turn
the route in the( route
location as perpath.
the given distance and time), and should not
jump, jerk, or change location after a few seconds.
Location must be updated after the internet connection is back
Location must be updated when the trip is not completed and login in to another device
During the live tracking uninstall and Install again and login into the application, the location must be updated.
Should be showing only one route after opening the application from the background.
 Should be showing only the respective driver car in the live tracking screen.

UI-Related
18
Scenarios
Check the right image sizes are shown in a good manner with Orientation.
Confirm that all Spell check is right on alert, error messages, error popup, and so on.
Confirm
Check thatthat
Onapp Logo(Single
Taping ought not
Tap)to Application
be blurred and titleApplication
Logo, of the App ought
Splashnot to be
must incorrectly
show spelled.
and it must not show up
more than four seconds.
Confirm that the app should not perform wrong activities while rendering or considering by making user input
Confirm
while thethat any sort
handset of text
or app ought
is busy withnotrendering
to be cutor
off.
processing. There should be no wrong response by the
Application.
Check that each screen ought to be visible for the time relevant to easily read all its data by moving between
screens of an
Check that app.messages should reveal to a user the characteristics of the issue and show what development
error
should
When thebe screen
made (where
permitssuitable).
the changing of information without saving, it must invite users to save in case they
move to another screen or record.
If the user removes an item, it’s a smart approach to confirm the user with the delete confirmation alert.
19 In-app purchase Should have a restore purchase option in the application except for the consumable in-app purchase.

Should have proper information about the in-app purchase and plan on the selling page of the in-app purchase.
Should have receipt validation implemented for in-app purchase.
Correct price and billing cycle information should be there on the buy now popup.
The purchased plan should not be renewed after canceling the subscription.
The premium/Lock
Should feature
be proper alert should
message be be unlocked
displayed or able
when to use
trying after successfully
to restore purchasing
a purchase without the plan.In-App
a complete
purchase.
Check the webhooks call for the canceled plan from payment gateway platforms like PayPal, Strike, etc.
Check auto-renew plan should be stopped after canceling auto-renew from the front end.
Should not be store user credit/Debit card information in our database.
Incoming calls, text messages, or notifications are your common examples of interrupt conditions. You need to
20 Interruption check how the app’s behavior when the interruption ends.
Localization & In case your app is multilingual, it should be tested in different languages to guarantee that there is no data
21
Time zone truncation issue, character encoding problem, or any UI issues because of fluctuating character lengths.

Ex. if application
If the the application is in Arabic
supports language
the Arabic thenthen
language the alignment should be from
select the application the right
language insteadasofwell
as Arabic the as
Left.
the
device language as Arabic & verify the app.
Check all the pop-up, notifications alert messages all links, static and dynamic pages are opening in the user-
selected language.
Localization -
22 Regional Date & time is formats are properly formatted for target region
Specification
Phone numbers formats are properly formatted for target region
Colors are appropriate and express the desired message.
Licenses and product names obey country-specific regulations.
Phone number provided should be accessible by the users of the targeted region.
Currency conversions and formats are handled appropriately.
Localization -
23 Terminology is consistency across the UI, help files & Documentation.
Language
Layout is consistent with the Source/English version.
Line Breaks & hyphenation are correct.
Localization -
24 Hyperlinks function properly.
Functionality
Hotkey is functional.
Entry field supports special characters.
 Validation of fields works properly (e.g Postal code for target region)
Lists are sorted according to target region & language.
25 Gesture Thoroughly test the multi-touch features such as pinch to zoom or pinch to shrink etc.
If
In user
case clicks
of backonnavigation
the back from home
if users page ofdata
unsaved theisapplication
getting loss user should
then go outshow
we should of thepop-up
application.
that on back
navigation
plain data will
address get lost.
Missing @ sign and domain
#@%^%#$@#$@#.com
Check the buttons with multiple Garbage
touch which are intended to work with single touch.
email@domain.com
@domain.com -- Validusername
Missing email
Check if user taps on the two buttons simultaneously.
firstname.lastname@domain.com
Joe Smith <email@domain.com> -- Email Encoded contains
HTML a dot in theemail
within address field
is invalid
check scroll and swipe
email@subdomain.domain.com
email.domain.com should
Missing @work-- smoothly
Email without
contains dotjerk.
with subdomain
firstname+lastname@domain.com
email@domain@domain.com -- Plus
Two @ sign
sign is considered valid character
26 Compatibility
email@123.123.123.123
.email@domain.com
To test user Interface of the Domain
Leading is
dot inon
application valid
addressIP address
various is screen
not allowed
sizes.
email@[123.123.123.123]Trailing
email.@domain.com Squaredot bracket
in address around
is not IP address is considered valid
allowed
To
Testtest your application
application supports
compatibility withvarious
various mobile devices
OS Test i.e different
applications manufacturer
compatibility with a combination of different
"email"@domain.com
email..email@domain.com Quotes around
Multiple email
dots is considered valid
devices and different
1234567890@domain.com OS. Digits in char address are valid
あいうえお@domain.com Unicode as address
email@domain-one.com
email@domain.com (Joe Smith) Dash in Text followingisemail
domain name validis not allowed
User-generated If your application has user-generated
_______@domain.com Underscore content
in the then the field
address Report Post / Report User/ Block use option is
is valid
27 email@domain Missing top level domain (.com/.net/.org/etc)
content mandatory ( connection
email@domain.name reason to apple
.name is dash rejection)
validinTop Level Domainisname
email@-domain.com Leading front of domain invalid
email@domain.co.jp
email@domain.web .web is not a valid top-levelname
Dot in Top Level Domain domainalso considered valid (use co.jp as an example here)
28 Valid Email Id firstname-lastname@domain.com
email@111.222.333.44444 InvalidDash in address field is valid
IP format
29 Invalid Email email@domain..com Multiple dot in the domain portion is invalid
30 Back Navigation If user is on the homepage of the application. click on the device back button pop-up should be there 'Do you
want to exit' or toast message should be shown.
Comments