Thursday, March 12, 2009

User Interface Testing

User Interface Testing:

User interface testing is defined as to test the interface between the application and the end user.
Here we will see how to test a simple form for user interface testing.



Steps for User Interface Testing:

1) Check with the spellings for all the labels
2) Check whether the Tab sequence is working properly in all the fields
3) Anyone option have to be selected as default in the Radio box
4) Able to select the options in the radio box by using right and left
arrows in the keyboard
5) Select option have to display as default in the combo box
6) It will not allow to enter a new option in the combo box
7) We can able to select the options in the list by using up and down
arrows in the keyboard
8) “ * “symbol have to display in all the mandatory fields
9) By clicking submit button without entering any texts, it have to
display error message in mandatory fields
10) By Clicking Cancel button it have to display the previous or home page
11) Font size should be proper as per the requirement
12) Font style should be proper as per the requirement
13) Spaces between the texts and the fields should be proper

If you know more about User Interface Testing, kindly write down in comments section or send an e-mail to me.

9 comments:

  1. To continue.
    Some of these are not UI tests but would have to tested anyway so while you are there...
    14) Input values for age test 9,10,30,31,0 and -1
    15) Screen size adjustments (Should be automatic but...)
    16) Copy /Paste
    17) Limits for Roll and Name High and low
    18) Products Single select or multiples?
    19) Products deselect

    ReplyDelete
  2. Also;

    deskcheck the database field types and lengths and match with UI permissable types and lengths.

    Eg. Name in database is varchar(100). Does the UI accept greater than 100.

    ReplyDelete
  3. Default focus should be on First field in the form

    ReplyDelete
  4. 20. Bobby drop tables...?

    ReplyDelete
  5. If we are talking about web UI testing we have to verify that entering special chars like ><'" does not break layoutsm views and tables in result page...

    ReplyDelete
  6. 21) Notes about what is acceptable should be valid (i.e. numbers only on name field)

    ReplyDelete
  7. Verify leading and trailing spaces are trimmed on submit

    ReplyDelete
  8. (Some of these are based on assumptions about the requireemnts or might indicate missing requirements)

    Why numbers and not letters in the *name* field?
    For every error that you test, is the error message always informative (or obscure)?
    If you submit valid info:
    - does it give the correct positive acknowledgement?
    - does it return to this window for additional submissions or return to a previous window?
    If you cancel:
    - Does it warn you that there is unsubmitted data which will be lost
    - Does the UI go back to the previous window?
    - If you resubmit the form will it blank all fields/reset to defaults, or does it cache the info from the previous submission (security concern)?
    Robustness testing:
    - Enter some data; restart the system; verify you can restart the application and there is no corruption of the database

    Ken.

    ReplyDelete
  9. change the font size in the browser and test if the field names and textboxes are aligned

    ReplyDelete