Re: [drupal-devel] two minor usability issues, introduced recently
We don't have usability tests -- how do you envision this to be done?
One hindrance in getting usability testing done is because the usability people are not necessarily technical people. When a new feature comes in as a patch, the usability expert has to patch his copy of Drupal, then get around to test it for usability. This is however not easily done, as I, for example, am a technical dufus with a little bit of coding skills. I am however majoring in usability, so, I can provide some usability testing but where and how? I have a possible solution for this issue. Before reading the proposed solution, keep in mind that it is only to stimulate thought, as I am not sure how technically feasible it is: 1. Set up a site based on HEAD. 2. Assign a technical person to update and maintain it. 3. When an update is applied (patch or other), simply add/update the a "changelog" or "issue" or something. 4. When a usability person analyzes the change, he documents it accordingly on the same issue. 5. Developers read the usability person's report and change the code if necessary. 6. Usability testers get access to test all new aspects of the page/page/feature/whatever. 7. Of course the database might need to be refreshed now and then. Regards, Kobus
On Sun, 25 Sep 2005, Kobus Myburgh wrote:
1. Set up a site based on HEAD. 2. Assign a technical person to update and maintain it. 3. When an update is applied (patch or other), simply add/update the a "changelog" or "issue" or something. 4. When a usability person analyzes the change, he documents it accordingly on the same issue. 5. Developers read the usability person's report and change the code if necessary. 6. Usability testers get access to test all new aspects of the page/page/feature/whatever. 7. Of course the database might need to be refreshed now and then.
I've taken another approach with one of my patches: Upload patched files. Got me some feedback I wouldn't have got otherwise. As long as not db change is involved this should be a simpler solution. Even if db changes are involved one could create a small test db. Cheers, Gerhard
Very often a simple screenshot gets interesting people involved. I agree that usability people are often not interested into patching, testing code etc. A screenhost can save me often half an hour fiddling, when I could have commented on a screenshot in five minutes. Ber On Sunday 25 September 2005 17:27, Gerhard Killesreiter wrote:
On Sun, 25 Sep 2005, Kobus Myburgh wrote:
1. Set up a site based on HEAD. 2. Assign a technical person to update and maintain it. 3. When an update is applied (patch or other), simply add/update the a "changelog" or "issue" or something. 4. When a usability person analyzes the change, he documents it accordingly on the same issue. 5. Developers read the usability person's report and change the code if necessary. 6. Usability testers get access to test all new aspects of the page/page/feature/whatever. 7. Of course the database might need to be refreshed now and then.
I've taken another approach with one of my patches: Upload patched files. Got me some feedback I wouldn't have got otherwise. As long as not db change is involved this should be a simpler solution. Even if db changes are involved one could create a small test db.
Cheers, Gerhard
participants (3)
-
Bèr Kessels -
Gerhard Killesreiter -
Kobus Myburgh