Checklist for ui or ux testing

Checklist on how we do UI/UX Testing

2017

Checklist for UI/UX Testing

QA Specialist TestOrigen Software Testing Pvt. Ltd. 1/1/2017

WWW.TESTORIGEN.COM

Page 1

Checklist on how we do UI/UX Testing

2017

General Principles Testing: General Principles Test Cases:

Tested by Tested on

Pass or Fail

Remarks

Pass or Fail

Remarks

1. Each activity that changes the user's information or application's settings can be fixed.

2. All application settings can be reestablished to their defaults without the user remembering what those defaults were.

3. After establishment, the application can be utilized without the client inserting a CD or disk at any time.

4. The most frequently utilized capacities are found at the best level of the menu structure.

Keyboard Navigation Testing: Keyboard Navigation Test Cases Tested by Tested on 1. Proficient keyboard access is given to all application features.

2. All windows have a logical keyboard navigation arrange.

3. The right tab order is utilized for controls whose empowered state is subject to checkboxes, radio buttons or flip buttons.

4. Keyboard access to applicationparticular capacities does not supersede existing framework accessibility features.

WWW.TESTORIGEN.COM

Page 2

Checklist on how we do UI/UX Testing

2017

5. The application gives more than one technique to perform keyboard assignments at whatever point conceivable.

6. There are elective key combinations wherever conceivable.

7. There are no clumsy reaches after regularly performed keyboard operations.

8. The application does not utilize redundant, synchronous keypresses.

9. The application gives keyboard reciprocals to all mouse capacities.

10. Any object or text that can be chosen with the mouse can likewise be chosen with the keyboard alone.

11. Any object that can be resized or moved with the mouse can likewise be resized or moved with the keyboard alone.

12. The application does not utilize any broad route capacities to trigger operations.

13. All keyboard conjured menus, windows and tooltips appear close to the object they identify with.

WWW.TESTORIGEN.COM

Page 3

Checklist on how we do UI/UX Testing

2017

Mouse Interaction Testing: Mouse Interaction Test Cases:

Tested by Tested on

Pass or Fail

Remarks

Pass or Fail

Remarks

1. No operations rely upon input from the privilege or middle mouse buttons.

2. All mouse operations can be wiped out before they are finished.

3. Visual criticism is given all through drag and drop operations 4. The mouse pointer is never distorted under application control, or its development limited to some portion of the screen by the application.

Graphical Elements Testing: Graphical Elements Test Cases:

Tested by Tested on

1. There are no hard-coded graphical traits, for example, line, and fringe or shadow thickness.

2. All multi-shading graphical elements can be appeared in monochrome just, where conceivable.

3. All intelligent GUI elements are effortlessly recognizable from static GUI elements.

4. An alternative to stow away superfluous graphics is given.

WWW.TESTORIGEN.COM

Page 4

Checklist on how we do UI/UX Testing

2017

Fonts and Text Testing: Textual styles and Text Test Cases:

Tested by Tested on

Pass or Fail

Remarks

1. No textual style styles or sizes are hard-coded.

2. An alternative to kill graphical backdrops behind text is given.

3. All labels have names that bode well when taken outside of context.

4. No label names are utilized more than once in a similar window.

5. Label positioning is steady all through the application.

6. All static text labels that distinguish different controls end in a colon (:).

7. Static content labels that distinguish different controls quickly go before those controls in the tab arrange.

8. Another option to WYSIWYG is given. For instance, the capacity to indicate diverse screen and printer textual styles in a content editor.

WWW.TESTORIGEN.COM

Page 5

Checklist on how we do UI/UX Testing

2017

Color and Contrast Testing: Color and Contrast Test Cases:

Tested by Tested on

Pass or Fail

Remarks

Pass or Fail

Remarks

1. Application hues are not hardcoded, but rather are drawn either from the present desktop subject or an application setting.

2. Color is just utilized as an improvement, and not as the main intends to pass on data or activities.

3. The application underpins all accessible high-differentiate themes and settings.

4. The software product is not reliant on a specific high-differentiate themes or settings.

Magnification Testing: Magnification Test Cases

Tested by Tested on

1. The application gives the capacity to amplify the work zone.

2. The application gives the alternative to scale the work region.

3. The application's functionality is not influenced by changing the magnification or scale settings.

WWW.TESTORIGEN.COM

Page 6

Checklist on how we do UI/UX Testing

2017

Audio Testing: Audio Test Cases:

Tested by Tested on

Pass or Fail

Remarks

Pass or Fail

Remarks

Pass or Fail

Remarks

1. Sound is not utilized as the main methods for delivering any things of data.

2. The client can design the frequency and volume of all sounds and cautioning beeps.

Animation Testing: Animation Test Cases:

Tested by Tested on

1. There are no blinking or flashing components with a frequency more than 2Hz or lower than 55Hz. 2. Any blinking or flashing is kept to small ranges of the screen.

3. If animation is utilized, an alternative is accessible to turn it off before it is first appeared.

Keyboard Focus Testing: Keyboard Focus Test Cases:

Tested by Tested on

1. At the point when a window is opened, focus begins at the most normally utilized control.

2. Current input focus position is obviously shown consistently.

3. Info focus is appeared in precisely one window constantly.

WWW.TESTORIGEN.COM

Page 7

Checklist on how we do UI/UX Testing

2017

4. Proper sound or visual feedback is given when the client endeavors to explore past either end of a gathering of related objects.

5. The default sound or visual cautioning signal is played when the client presses a wrong key.

6. There is adequate sound data for the visual concentration that the client can make sense of what to do next.

7. When utilizing assistive advances, for example, a screen peruser or Braille gadget, the present program demonstrates the position and substance of the visual focus pointer.

Timing Testing: Timing Test Cases:

Tested by Tested on

Pass or Fail

Remarks

1. There are no hard-coded timebased or time-outs features in the application.

2. The hiding or displaying of essential data is not activated exclusively by development of the mouse pointer.

WWW.TESTORIGEN.COM

Page 8

Checklist on how we do UI/UX Testing

2017

Documentation Testing: Documentation Test Cases:

Tested by Tested on

Pass or Fail

Remarks

1. All documentation is in an available configuration; with textual option depictions accommodated all figures and outlines.

2. The documentation incorporates a segment that covers all the application's availability features.

WWW.TESTORIGEN.COM

Page 9