Android Apps Test Cases for UI Related Scenarios



Android Apps Test Cases for UI Related Scenarios

Following are the major test cases for UI scenarios for an Android App :-

  1. Confirm the Alignment of screen, it should be proper and exact as per available sizes. Expected Result: Proper Alignment should be there.
  2. Confirm for each & every button, image Pixel as per wire frame or page screen blueprint or schematic, Expected Result: Dimensions mentioned in wire-frame should be same as it is.
  3. Make sure that correct image sizes displayed in well manner with the orientatioin.
  4. Confirm that all spells are ok and correct on Alerts, Error messages, error pop ups etc.
  5. Confirmed the spinners i.e. types, sizes, should be suitable as per available screen.
  6. Confirm and make sure that logo of apps should not be blurred and application title should not be wrong spells.
  7. Confirm and make sure for consistent font Sizes.
  8. Make sure that any type of text should not cut off.
  9. Confirm and make sure that apps must not perform incorrect action while rendering or thinking by making user input while the app or handset is busy for rendering or processing. There must not be incorrect reaction by the apps.
  10. Confirm graphics should not be blurred, it should be checked on different -2 resolution Devices. (Like BB have different resolutions for its all types of device, iPhone 4 or iPhone 3Gs)
  11. Confirm that on Taping Apps logo (Single Tap), Application Splash should show.
  12. Confirm and make sure that app splash must not show more than 4 sec.
  13. Confirm that there should be visual feedback when responses for any action take more than 3 second.
  14. Make sure that each and every screen should be visible for necessary time to comfortable read all its info by moving in between the screen of an app. Each screen must be display for the necessary time to comfortable read all its info.
  15. Make sure that error message displaying on apps must be clearly visible and understanable.
  16. Also confirm that error message is clearly explainable to user as the nature of the problems, and it will also indicate that what action and when need to to be taken.
  17. Confirm any selected function in the application which should start with in the 5 sec.
  18. Some visual indication should be there that the function is being performed like:
    - User input prompting
    - showing progress bars or splash screens
    - showing text such as “Wait ...” etc
  19. Make sure that if screens require data entry on any specific fields, then it should identify the mandatory fields with red mark or asterisk and should generate a friendly warning if the record left blank.
  20. Make usre that required screens includes numeric, dates, currency or any other specific data type to ensure that only valid data or record can be input.
  21. Confirm and make sure that screens includes text box that allow the data entry need to ensure that the width of data entered does not exceed the width of the field table.

MOBILE APPS    QTP TESTING QUESTIONS  MANUAL TESTING  ANDROID APPS


No comments:

Post a Comment

Popular Posts