Mobile Application Testing CheckList

Mobile App Checklist
S.No	Category	Test Steps	Status
1	Installation	Install the application being tested:
		The application must install without error.
2	Installation	During installation note the version number presented to the user.
		The version number must match that specified during submission.
3	Installation	Verify that the application has successfully installed on the device by navigating to the area on the phone where new applications are installed.
		The application should present one or more icon(s) on the phone.
4	Installation	On clicking the icon of the app, it should load its content within 20 seconds as per the global standards.
5	Installation	On clicking the icon of the app in the settings area, it should load its content within 3 seconds as per the global standards.
6	Installation	Should check other existing application in the device, to ensure they are not affected cause of the new application.
7	Installation	Application should be arranged in the alphabetical order.
8	Installation	What happens when we get a call during the installation, it should pause and resume the process after the call ends.
9	Installation	It should show the sms notifications.
10	Installation	Verify that the application continues installing process even after the
		screen of the mobile is locked.
11	Installation	Verify that the installation of the application continues after an
		interuption by a voice call or text.
12	Installation	Verify that if other applciations are working with the same performance while the installation process is going on.
13	Installation	Verify that the application installs within a specified time limit.
1	Un-install	Stop the application as described in Test 2 and uninstall the application using the system installer.
		The application must be uninstalled without error.
2	Un-install	Following the same steps as in Test 1, navigate to where you would expect to see the application icon.
		The application icon must not longer be present on the device.
3	Un-install	If you used another method to verify successful installation in Test 1 then use this method to ensure that the application has been uninstalled.
4	Un-install	Using the same file manager as at the start of Test 1 check that the amount of user space available on the device is either the same as that found in step 1 or that any difference between the space available before and after fulfills the following criteria.
		a) Excluding user-generated and downloaded content, the application leaves no more than 100Kb of data on the phone after uninstall.
		b) Any data left on the device after install matches the explanation given during the submission process.
5	Un-install	Check other existing application weather on un-installing the new app affects them.
6	Un-install	What happens when we get a call during the installation, it should pause and resume the process after the call ends.
7	Un-install	It should show the sms notifications.
8	Un-install	It should show the app is un-installed sucessfully
9	Un-install	Time taken to un-install the app should follow the global standards.
10	Un-install	Un-installing an application should not have any effects on peformance of other application.
11	Un-install	Should show notification message about the successful unistallation process of the application
12	Un-install	The application should ask for security options(eg: Password) if predefined during the uninstallation process.
13	Un-install	The application should ask for a confirmation for uninstallation through a notification before proceeding to uninstallation.
14	GUI	Check for Alignment.
15	GUI	See each and every buttons, images Pixels as per wire frame (Some clients very sticky to their wireframes), Means they need exactly (Pixel by pixels) what they have in wire frame.
16	GUI	UI should be User Friendly.
17	GUI	UI should be not break. (Check for orientation too)
18	GUI	Proper images size displayed in well manner with Orientation.
19	GUI	Spell check (Check on Alert, error popup too)
20	GUI	Font size should be consistent
21	GUI	Any kind of text should not be cutting off
22	GUI	Are fonts too large or too small to read?
23	GUI	Are graphics being used the most efficient use of file size? (Any kind of images should not be blurred)
24	GUI	Consistent, clearly recognizable good "look-&-feel"
25	GUI	Check with different resolution Devices (Like BB have Different resolution for all devices, iPhone 3Gs or iPhone 4)
26	GUI	Spinner (Size, Types) should be suitable as per screen.
27	GUI	Check for application Logo (Should not be blurred and App title should not be … (Means whole logo text should be displayed))
28	GUI	• Required Fields:
		If the screen requires data entry on a specific field, should identify the required fields with a red asterisk and generate a friendly warning if the data is left blank.
29	GUI	• Data Type Errors:
		If the screen contains dates, numeric, currency or other specific data types, ensure that only valid data can be entered.
30	GUI	• Field Widths:
		If the screen contains text boxes that allow data entry, ensure that the width of data entered does not exceed the width of the table field.
31	GUI	• Onscreen Instructions:
		If the information in the screen is not self-explanatory to the casual user, should provide onscreen instructions to aid the user.
32	GUI	• Progress Bars:
		If the screen takes more than 5 seconds to display the results/page, it should contain a progress bar so that the user understands the processing is continuing.
33	GUI	• Cosmetic Inconsistencies:
		The screen look, feel, and design should match the other screens in your application. (Application should match with the Wireframe or design document provided).
34	GUI	• Abbreviation Inconsistencies:
		If the screens contain abbreviations (e.g. Nbr for number, Amt for amount, etc), the abbreviations should be consistent for all screens in the application.
35	GUI	• Save Confirmations:
		If the screen allows changing of data without saving, it should prompt users to save if they move to another record or screen.
36	GUI	• Delete Confirmations:
		If a person deletes an item, it is a good idea to confirm the delete. User should be prompted with confirmation alert.
37	GUI	• Type Ahead:
		If the user interface uses combo boxes (drop down lists), be sure to include type ahead (if there are hundreds of items in a list, users should be able to skip to the first item that begins with that letter when they type in the first letter).
38	GUI	• Grammar and Spelling:
		Ensure the test cases look for grammar or spelling errors.
39	GUI	• Table Scrolling:
		If the application lists information in table format and the data in the table extend past one page, the scrolling should scroll the data but leave the table headers intact.
40	GUI	• Error Logging:
		If fatal errors occur as users use your application, ensure that the application writes those errors to a log file, event viewer, or a database table for later review. Log the routine the error was in, the person logged on, and the date/time of the error.
41	GUI	• Error Messages:
		Ensure that error messages are informative, grammatically correct, and not condescending.
42	GUI	• Shortcuts:
		If the application allows short cut keys for copy/paste etc, should test each and every short cuts.
43	GUI	• Invalid Menu Items:
		Do not show menu items that are not available for the context users are currently in.
44	GUI	• Dialog Box Consistency:
		Use a style guide to document what choices are available for dialog boxes. Application should not have Save/Cancel dialog on one screen and an OK/Cancel on another. This is inconsistent.
45	GUI	• Screen Font Type:
		Ensure that the screen font family matches from screen to screen. Mismatching fonts within the same sentence and overuse of different fonts can detract from the professionalism of your software user interface.
46	GUI	• Screen Font Sizes:
		Ensure that the screen font sizes match from screen to screen. A good user interface will have an accompanying style guide that explicitly defines the font type and size for headers, body text, footers, etc.
47	GUI	• Colors:
		Ensure that screens do not use different color sets as to cause an inconsistent and poorly thought-out user interface design. Your style guide should define header colors, body background colors, footer colors, etc.
48	GUI	• Icons:
		Ensure that icons are consistent throughout your application by using a common icon set. For example, a BACK link that contains an icon next to it should not have a different icon on one screen versus another. Avoid free clip-art icons; opt for professionally designed icons that complement the overall look and feel of your screen design.
49	GUI	• Narrative Text:
		Having narrative text (screen instructions) is a great way to communicate how to use a specific screen. Ensure that narrative text appears at the same location on the screen on all screens.
50	GUI	• Brevity:
		Ensure that narrative text, error messages and other instructions are presented in laymen’s terms but are brief and to-the-point.
51	GUI	• Links:
		If your application has links on the screen (e.g. Save as Spreadsheet, Export, Print, Email, etc.), ensure that the links have consistent spacing between them and other links, that the links appear in the same order from screen to screen, and that the color of the links are consistent.
52	GUI	• Menus:
		If your application has menu items, ensure that menu items that are not applicable for the specific screen are disabled and the order in which each menu item appears is consistent from screen to screen.
53	GUI	• Buttons:
		If your application has buttons (e.g. Submit, OK, Cancel, etc), ensure that the buttons appear in a consistent order from screen to screen (e.g. Submit then Cancel).
54	GUI	Each field should get highlighted when the cursor is in that field
55	GUI	Minimize and restoring functionality should work properly
56	GUI	Tabbing will go onto the next editable field in the window
57	Functional	Check that the link takes you to the page it said it would.
58	Functional	Ensure to have no orphan pages (a page that has no links to it)
59	Functional	Check all of your links to other websites
60	Functional	Are all referenced web sites or email addresses hyperlinked?
61	Functional	If we have removed some of the pages from our own site, set up a custom 404 page that redirects your visitors to your home page (or a search page) when the user try to access a page that no longer exists.
62	Functional	Check all mailto links and whether it reaches properly
63	Functional	Acceptance of invalid input
64	Functional	Optional versus mandatory fields
65	Functional	Input longer than field allows
66	Functional	Radio buttons
67	Functional	Default values on page load/reload (Also terms and conditions should be disabled)
68	Functional	Is Command Button can be used for Hyperlinks and Continue Links?
69	Functional	Is all the data’s inside combo/list box are arranged in chronological order?
70	Functional	Are all of the parts of a table or form present? Correct layout? Can you confirm that selected texts are in the "right place?
71	Functional	Does a scrollbar appear if required?
72	Functional	Is the Privacy Policy clearly defined and available for user access?
73	Functional	At no point of time the system should behave awkwardly when an invalid data is fed
74	Functional	Check to see what happens if a user deletes cookies while in site
75	Functional	Check to see what happens if a user deletes cookies after visiting a site
76	Functional	Check the maximum field lengths to ensure that there are no truncated characters?
77	Functional	If numeric fields accept negative values can these be stored correctly on the database and does it make sense for the field to accept negative numbers?
78	Functional	If a particular set of data is saved to the database check that each value gets saved fully to the database. (i.e.) Beware of truncation (of strings) and rounding of numeric values.
79	Functional	Assure that leap years are validated correctly & do not cause errors/miscalculations.
80	Functional	Assure that Feb. 28, 29, 30 are validated correctly & do not cause errors/ miscalculations.
81	Functional	Is copyright for all the sites includes Yahoo co-branded sites are updated.
82	Functional	Assure that lowest and highest values are handled correctly.
83	Functional	Assure that numeric fields with a blank in position 1 are processed or reported as an error.
84	Functional	Assure that fields with a blank in the last position are processed or reported as an error an error.
85	Functional	Assure that both + and - values are correctly processed.
86	Functional	Assure that division by zero does not occur.
87	Functional	Include value zero in all calculations.
88	Functional	Assure that upper and lower values in ranges are handled correctly. (Using BVA)
89	Functional	Use blank and non-blank data.
90	Functional	Include lowest and highest values.
91	Functional	Include invalid characters & symbols.
92	Functional	Include valid characters.
93	Functional	Include data items with first position blank.
94	Functional	Include data items with last position blank.
95	Functional	Navigation should work correctly with the input methods offered by the device.
96	Functional	An application for a touch device should use touch interaction to navigate all functions/screens of the application, e.g. tapping buttons, navigating lists etc.
97	Functional	All interactive elements such as buttons must respond to touch interaction on first use. It must not be difficult to touch an interactive element, such as a button, link, image, etc.
98	Functional	Check weather all requirements and checkpoints are covered.
99	Functional	Give multiple inputs (Text inputs) at a time and the app should work according to that.
100	Functional	Check weather the app works in low memory available in the device.
101	Functional	Check the app weather it sync with native fucntionalities.
102	Functional	Whether checks for optional and mandatory fields carried out like a mandatory field should not be left blank and an optional should allow the user to skip the field.
103	Functional	Whether cookies are enabled according to the requirement of the project?
104	Functional	Whether Hot Keys, Control Keys for menus or actions are present or not?
105	Functional	Whether any broken links are present or not?
106	Functional	Closing of the application should result in “Are you sure?” message.
107	Functional	The application should ask for a sign in page after clearing the predefined cookies for accessing a social media
108	Functional	Verify if the application force closes for multiple jestures of the users
109	Functional	Verify if the application continous from the same place after minimizing and restarting it.
110	Functional	With the application installed and running use a second phone to call the test device.
		The incoming call must be indicated to the user on the test device.
111	Security	Does the site prompt for user name and password?
112	Security	Are concurrent logins permitted?
113	Security	Does the application include time-outs due to inactivity?
114	Security	Is bookmarking disabled on secure pages?
115	Security	Does your server lock out an individual who has tried to access your site multiple times with invalid login/password information?
116	Security	What happens when time out is exceeded? Are users still able to navigate through the site?
117	Security	Relevant information is written to the log files and that the information is traceable.
118	Security	Is confidentiality/user privacy protected?
119	Security	Have you verified where encryption begins and ends?
120	Load	Increase the number of users and keep the data constant.
121	Load	Does the home page load quickly? within 8 seconds
122	Load	Is load time appropriate to content, even on a slow dial-in connection?
123	Load	Can the site sustain long periods of usage by multiple users?
124	Load	Have you defined standards for response time (i.e. all screens should paint within 10 seconds)?
125	Load	Many users requesting a certain page at the same time or using the site simultaneously
126	Volume	Increase the data by having constant users
127	Volume	Will the site allow for large orders without locking out inventory if the transaction is invalid?
128	Volume	Can the site sustain large transactions without crashing?
129	Stress	Increase both number of users and the data
130	Stress	Performance of memory, CPU, file handling etc.
131	Stress	Error in software, hardware, memory errors (leakage, overwrite or pointers)
132	Stress	Verify that the application is able to meet the requirements and does not run out of memory or disk space.