Hi Matthew and list, just one more question: > 1. Brainstorm some tasks that could be tested in half an hour or so. > For example, importing a photo from a digital camera and sending it > to a friend. Or subscribing to a podcast and syncing it to a > portable music player. Or finding an interesting game to play. Or > printing a picture. > > 2. Follow standard user testing procedure to produce a test script > based on the task you choose, and post it to this list for others to > review it. (See for example Rubin & Chisnell, "Handbook of > usability testing" 2nd edition, chapter 8.) What about complex test scenarios ... i.e., not for usability test the way it's described in Rubin&Cisnell, but more for testing purposes? E.g., import photos from camera, edit in the GIMP, ... Scenarions which correspond to everyday usage but may bring out more complexity than single-program use cases, I mean. Do such scenarions exist, and would the be of interest? (When I used to work at a software company, the QA department had a lot of those which all had to pass in order for the software to be released).
Attachment:
signature.asc
Description: This is a digitally signed message part