Difference between revisions of "CEED UX testing"
(2 intermediate revisions by the same user not shown) | |||
Line 4: | Line 4: | ||
== Volunteers == | == Volunteers == | ||
− | + | * Jorge Avila | |
== The process == | == The process == | ||
All participants will use their favourite screen casting software and record how they use CEED and how they perform tasks that each of the tests give them. I ask them not to prepare anything in advance because the aim is to make intuitive tools with very flat learning curve. Ideally they would record it first try and submit the results. Commentary or annotation would be helpful but are not required. If you fail at some of the tasks, definitely submit the results, I want to know what you tried and where I should move the buttons so most people find the options. | All participants will use their favourite screen casting software and record how they use CEED and how they perform tasks that each of the tests give them. I ask them not to prepare anything in advance because the aim is to make intuitive tools with very flat learning curve. Ideally they would record it first try and submit the results. Commentary or annotation would be helpful but are not required. If you fail at some of the tasks, definitely submit the results, I want to know what you tried and where I should move the buttons so most people find the options. | ||
− | |||
− | |||
== Result submission == | == Result submission == | ||
Line 23: | Line 21: | ||
=== Project management === | === Project management === | ||
− | * to make your life easier, add the created imageset to a project targetted at CEGUI 0.8 | + | * to make your life easier, add the created imageset to a new project targetted at CEGUI 0.8 |
* make sure all paths are proper (you can copy the stock datafiles, no need to use anything custom as that would be very time consuming | * make sure all paths are proper (you can copy the stock datafiles, no need to use anything custom as that would be very time consuming | ||
Latest revision as of 17:02, 24 February 2012
The unified editor is slowly but surely getting useful. I think it's time we do user experience testing and see which features are hard to access and which workflows users will use (so that we can optimise for them).
Testing will be done on 2 of the "mostly finished" editors within CEED - imageset and layout editors.
Contents
Volunteers
- Jorge Avila
The process
All participants will use their favourite screen casting software and record how they use CEED and how they perform tasks that each of the tests give them. I ask them not to prepare anything in advance because the aim is to make intuitive tools with very flat learning curve. Ideally they would record it first try and submit the results. Commentary or annotation would be helpful but are not required. If you fail at some of the tasks, definitely submit the results, I want to know what you tried and where I should move the buttons so most people find the options.
Result submission
Ideally you would send the results to me in WebM and Theora in Ogg or other container. If you send the results in a different set of formats I will deal with it and convert it. Make sure you are OK with your work being used like this, I will include it as an attachment in my thesis. You will of course be credited accordingly. I require the submission to be licensed under CC-BY-SA license, with your name attributed
Tests
Imageset editing
- create a new imageset using [CHOOSE AN IMAGE]
- outline all of the elements in the image, name them Image1, Image2, Image3 and Image4
- choose two of the images and centre their offset (so that it is perfectly in the centre of the image)
- create one additional outline that takes the whole image, name it "All"
- ...
Project management
- to make your life easier, add the created imageset to a new project targetted at CEGUI 0.8
- make sure all paths are proper (you can copy the stock datafiles, no need to use anything custom as that would be very time consuming
Layout editing
(use the project you created in the previous test, with your favourite skin)
- create a form that will allow you to order a pizza for Crazy Eddie (with options)
- create another layout that will allow you to order a cabbage-like vegetable for Crazy Eddie (hint hint: maybe you can reuse parts of the previous form?)
- make sure the elements are positioned precisely