| Line 1: | Line 1: | ||
= MeeGo QA-tools User Experience = | = MeeGo QA-tools User Experience = | ||
| - | This is the main page for user experience (UX) work done for MeeGo QA-tools. The purpose of the UX activities is to improve the QA-tools so that they are easier, more efficient and more pleasant to use. | + | This is the main page for user experience (UX) work done for MeeGo QA-tools. The purpose of the UX activities is to improve the QA-tools so that they are easier, more efficient and more pleasant to use. For this, end-user feedback is crucial. |
| - | + | This page is meant for UX task list and other UX-related content, such as UX evaluation reports and UI drafts for discussion among the community. Even if some traditional user-centered design methods (user studies, usability tests etc.) require offline working, the results of those should be published here or be directly filed as enhancements/bugs to Bugzilla. | |
== Ongoing Work== | == Ongoing Work== | ||
* Testrunner-UI | * Testrunner-UI | ||
| - | ** | + | ** Design UI improvements based on user feedback |
| - | ** | + | ** Report the improvement proposals to Bugzilla |
== Need for Future Work == | == Need for Future Work == | ||
| + | |||
| + | * Every Tool | ||
| + | ** Check the end-user documentation | ||
| + | ** Evaluate the ease of the installation and the first time use | ||
| + | ** Improve visual look of the GUI tools, e.g. improve graphics | ||
| + | |||
* MIN | * MIN | ||
** Evaluate the graphical UI | ** Evaluate the graphical UI | ||
** Design UI improvements | ** Design UI improvements | ||
| + | *** If there is a need for a bigger UI renewal, different layout drafts should be provided for further discussion | ||
| + | ** Report the improvement proposals to Bugzilla | ||
| + | |||
| + | |||
| + | * Testrunner-lite and Testrunner-UI | ||
| + | ** Gather more end-user feedback | ||
| + | ** Design GUI for creating and editing test definition files | ||
== How to Participate == | == How to Participate == | ||
| - | UX work is no different from the other development work of QA-tools. | + | The UX work is no different from the other development work of QA-tools. You can, for instance, work on the tasks presented on this page or just propose new tasks. In general, the best channels for participating are: |
* [http://webchat.freenode.net/?channels=meego-qa-tools #meego-qa-tools IRC channel on irc.freenode.net] for discussing about the tools | * [http://webchat.freenode.net/?channels=meego-qa-tools #meego-qa-tools IRC channel on irc.freenode.net] for discussing about the tools | ||
* [http://bugs.meego.com/enter_bug.cgi?product=Development%20Tools Bugzilla] for reporting enhancement ideas or usability problems | * [http://bugs.meego.com/enter_bug.cgi?product=Development%20Tools Bugzilla] for reporting enhancement ideas or usability problems | ||
Contents |
This is the main page for user experience (UX) work done for MeeGo QA-tools. The purpose of the UX activities is to improve the QA-tools so that they are easier, more efficient and more pleasant to use. For this, end-user feedback is crucial.
This page is meant for UX task list and other UX-related content, such as UX evaluation reports and UI drafts for discussion among the community. Even if some traditional user-centered design methods (user studies, usability tests etc.) require offline working, the results of those should be published here or be directly filed as enhancements/bugs to Bugzilla.
The UX work is no different from the other development work of QA-tools. You can, for instance, work on the tasks presented on this page or just propose new tasks. In general, the best channels for participating are: