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