How to test user interface
Usability is the measure of a product’s potential to accomplish the goals of the user. In information technology, the term is often used in relation to software applications and Web sites, but it can be used in relation to any product that is employed to accomplish a task (for example, a toaster, a car dashboard, or an alarm clock). In this user interface test article we will see how to test usability of software and web interfaces. This web interfaces testing checklist will help you to derive interface test cases easily.
1.1 GUI Testing (COLORS):
1.1.1 Make sure the hyperlink color is standard. Until specified explicitly it should be blue.
1.1.2 The text field, input fields background color must be proper.
1.1.3 Fields which prompt message box etc have the correct color.
1.1.4 Are the screen and field colors adjusted correctly for non-editable mode? Should be grayed out.
1.1.5 Does the site use (approximately) standard link colors?
1.1.6 Are all the buttons are in standard format and size?
1.1.7 Is the general screen background has the correct color?
1.1.8 Is the page background (color) distraction free?
1.2.1 All fonts to be the same
1.2.2 Are all the screen prompts specified in the correct screen font?
1.2.3 Does content remain if you need to go back to a previous page, or if you move forward to another new page?
1.2.4 Is all text properly aligned?
1.2.5 Is the text in all fields specified in the correct screen font?
1.2.6 Is all the heading are left aligned
1.2.7 Does the first letter of the second word appears in lowercase? Eg: Testing
1.3.1 Are all graphics properly aligned?
1.3.2 Are graphics being used the most efficient use of file size?
1.3.3 Are graphics optimized for quick downloads?
1.3.4 Assure that command buttons are all of similar size and shape, and same font & font size.
1.3.5 Banner style & size & display exact same as existing windows.
1.3.6 Does text wrap properly around pictures / graphics?
1.3.7 Is it visually consistent even without graphics?
1.4.1 Is all the error message text spelt correctly on this screen?
1.4.2 Is all the micro-help text tool tip spelt correctly on this
1.4.3 Microhelp text (ie tool tip) for every enabled field button
1.5.1 Are all disabled fields avoided in the TAB sequence?
1.5.2 Are all read-only fields avoided in the TAB sequence?
1.5.3 Can all screens accessible via buttons on this screen be accessed correctly?
1.5.4 Does a scrollbar appear?
1.5.5 Does the Tab Order specified on the screen go in sequence from Top Left to bottom right? This is the default unless otherwise specified.
1.5.6 Is there a link to home on every single page?
1.5.7 On open of tab focus will be on first editable
1.5.8 When an error message occurs does the focus return to the field in error when the user cancels it?
1.6 USABILITY Test Cases
1.6.1 Are all the prompts field spelt correctly?
1.6.2 Are fonts too large or too small to read?
1.6.3 Names in command button & option box names are not abbreviations.
1.6.4 Assure that option boxes, option buttons, and command buttons are logically grouped together in clearly demarcated areas “Group Box”
1.6.5 Can the typical user run the system without frustration?
1.6.6 Do pages print legibly without cutting off text?
1.6.7 Does the site convey a clear sense its intended audience?
1.6.8 Does the site have a consistent, clearly recognizable “look-&-feel”?
1.6.9 Does User can Login to the Member Area with both UserName / Email ID?
1.6.9 Does the site look good on 640 x 480, 600×800 etc.?
1.6.10 Does the system provide or facilitate customer service?
1.6.11 Is all terminology understandable for all of the site intended users?