Android App Test Cases (UI Related Scenarios)

• Verified that Alignment should be proper.Expected result: Alignment should be proper.
• Check each and every buttons, images Pixels as per wire frame/page schematic or screen blueprint.Expected result: Dimensions must be same as defied in wireframe.
• Verify that Proper images size displayed in well manner with Orientation.
• Verify that all Spell check are correct on Alert, error popup,Error messages etc.
• Verified that Spinner (Size, Types) should be suitable as per screen.
• Verify that application Logo should not be blurred and App title should not be misspelled (Means whole logo text should be displayed))
• Verify that Font size should be consistent.
• Verify that any kind of text should not be cutting off.
• Verify that any kind of graphics should not be blurred, Check with different resolution Devices (Like BB have Different resolution for all devices, iPhone 3Gs or iPhone 4)
• Verify that application must not perform inappropriate actions while thinking or rendering by making user input while the application or handset is busy processing or rendering.There must be no inappropriate reaction by the Application.
• Verify that On Taping (Single Tap) Application Logo , Application Splash should display.
• Verify that Application Splash Should not display More than 4 Second
• Verify that there is visual feedback when response to any action takes more than 3 seconds.
• Verify that each screen should be visible for the time necessary to comfortably read all its information by moving between screens of an application. Each screen must be visible for the time necessary to comfortably read all its information.
• Verify that error messages in the Application must be clearly understandable.
• Verify that error messages must clearly explain to a user the nature of the problem, and indicate what action needs to be taken (where appropriate).
• Verify that any function selected in the Application should start within 5 seconds.
• Verify that there must be some visual indication that the function is being performed like
•  – prompting for user input;
• - displaying splash screens or progress bars;
• - displaying text such as “Please wait…”, etc
• Verify that 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
• Verify that If the screen contains dates, numeric, currency or other specific data types, ensure that only valid data can be entered.
• Verify that 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.
• If the information in the screen is not self-explanatory to the casual user, should provide onscreen instructions to aid the user.
• 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.
• The screen look, feel, and design should match the other screens in your application. (Application should match with the Wireframe or design document provided).
• 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.
• If the screen allows changing of data without saving, it should prompt users to save if they move to another record or screen.
• If a person deletes an item, it is a good idea to confirm the delete. User should be prompted with confirmation alert.
• 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).
• Ensure the test cases look for grammar or spelling errors.
• 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.
• 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.
• Ensure that error messages are informative, grammatically correct, and not condescending.
• If the application allows short cut keys for copy/paste etc, should test each and every short cuts
• Do not show menu items that are not available for the context users are currently in.
• 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.
• Ensure that the screen font family matches from screen to screen. Mismatching fonts within the same sentence and overuse of different fonts is not allowed.
• 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.
• Ensure that screens do not use different color sets as to cause an inconsistent.style guide should define header colors, body background colors,screen background color, footer colors, etc.
• 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.
• Ensure that narrative text appears at the same location on the screen on all screens.
• Ensure that narrative text, error messages and other instructions are presented in laymen’s terms but are brief and to-the-point.
• 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.
• 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.
• 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).
• Tabbing will go onto the next field on the screen