Usability Testing

10 tips for usability testing

Usability Testing

We want to present you ten rules for usability testing. The founder of those rules is Jakob Nielsen (one of the “Nielsen Norman Group” directors). He formulated it in 1990, but it is still has not lost topicality. These rules name as “Ten Usability Heuristics” and you can read it below:

Awareness of the state of the system

If something happens in the system user must know about this process and be aware fully of all defects. The cooperation between the user and the system should be logic and functional.

The similarity of the real world

The communication language between the user and the system must be recognized by the user. It is better to use familiar to user phrases and words than specialized terms. It is a good solution of providing more natural form of the information.

Freedom of action

The system must always provide a “path of retread” to users by giving the ability to return to the prior action, so they need to make minimum movements to correct the defect.

Uniformity and standards

Keep up the uniformity and do not describe the same thing in different terms.

Avoiding mistakes

Minimize the amount of the conditions which could make mistakes and require the user to confirm own actions in a case of mistake. This is helps to avoid errors.

In the mind, and not in memory

Do not force users to keep in memory various large unnecessary information about numbers or options, to shift the place of this information. The manual should always be easily accessible in any time when some difficulties could happen.

Flexibility and efficiency

Do not give too much information to experienced users, let they make repetitive actions to accelerate the process and try to hide these from the inexperienced user.

Aesthetic and minimalist design

Do not put in your dialogs irrelevant information it could make perception of the essence more difficult.

Understanding the problems and their solution

The expression of error messages must be understandable for users, they have to be able to describe the defect and make actions to solve it.

Reference material and documentation

Reference materials must be informative, contain only necessary information and be easy to find it, because in the working process the background information may still be needed.


TestFort Blog

About TestFort Blog

TestFort blog is an official blog of TestFort QA Lab company and is dedicated to various QA and software testing issues.


no comments yet

Be the first to comment this post!

Would you like to share your thoughts?

Software testing & QA blog by TestFort © 2017

×