OHT+Inspector: The Usability Compiler (open-source)
Imagine a usability compiler. A compiler in which the input is a GUI, and the output a collection of errors and warnings referring to usability glitches that have to be fixed. This is the OHT+Inspector.
The OHT+Inspector is an open-source Usability Evaluation Tool whose aim is to perform a reviewing process over a GUI based on a set of constraints and guidelines. Some examples of guidelines can be:
- all the widgets in a GUI have to follow a tab-order
- all the tooltip texts have to be filled
- the separation between elements is equal or higher than 3px
This process is usually conducted manually. However, the OHT+I encapsulates the knowledge of the usability experts and automate the inspection process. It works as follows:
- The tester selects the evaluators to be executed.
- The tool analyses the properties of a GUI by using GUI instrospection
- Those properties are used to create an abstract GUI composed of elements and roles
- A list of previously chosen constraints and guidelines are checked against the abstract GUI
The process is based on a set of usability evaluators, which return a set of reports including the errors/warnings discovered, and in some cases advices to fix them. These reports are stored in a usability inspection project for further analysis. The tool also allows the tester to export the obtained reports to a PDF document and other open formats.
This prototype can be easily extended in order to add new usability evaluators to check new GUI properties or more complex constraints; it also could be extended to fit it to other testing environments where, for example, other windowing system is used.
For further information, videos, and download links, please visit the "Cátedra SAES":http://www.catedrasaes.org/trac/wiki/ProjectsOhtPlus#OHTInspector website:
[EDIT: fixed image links, Volker]
Looks interesting like other your projects.
Volker, thank you very much for fixing the image links!!!!
Maybe once you have successfully downloaded and compiled the project, you attempt to execute it and it does not work fine. The problem is that the testing module did not find the “libCSU” library, so you need to update the LD_LIBRARY_PATH environment variable in the following way:
where “xxxxxxxxx” is the folder in which the prototype was installed.
I hope it will help you to solve the problem, and do not hesitate to send a nes post if you need further help.ç
Better solution is
if [ "x$LD_LIBRARY_PATH" = "x" ]; then
Replace LD_LIBRARY_PATH with DYLD_LIBRARY_PATH on Mac OS X.
Empty parts in LD_LIBRARY_PATH can be dangerous, see the discussion in "this forum thread":http://developer.qt.nokia.com/forums/viewthread/3064/#19695.