CONDUCTING A TEST #11
Conducting the test
Preparation/Introduction:
Conducting the test:
The tester should describe the way the test will be run and give specific instructions about whether the user must notify the tester when they are finished or not. They should also explain their role thoroughly, whether they will answer questions or not, why they are there, etc.. The tester should also remind the user that it is the product being tested, not the user.
Unless it is interactive type testing, testers should refrain from interacting or interupting the user. It is a very difficult to learn to refrain from helping, making any noise or body movement that may give a clue to a struggling user.
Testers should step in when a user becomes stuck and is becoming upset with a task.
Testers and observers should record as many observations as possible. These notes could contain noted mistakes, errors, user questions/comments, bizarre product response/bug , physical difficulties, user frustrations, time taken to do tasks, body posture, number of calls to help desk etc. Basically record anything you believe may be important. If you are using a videotape you could just note the time at which something happened and a brief note, then review the tape and record details later. The testers must also remember to be recording any performance measure they had planned on taking (sometimes you can get caught up in watching the user).
Debriefing:
At this time the user should be asked to fill out any post quetionnaires. After the questionnaire has been completed the user should be encouraged to ask questions or give comments on their experience. The testers can also take advantage of this time and ask the user any questions about the test tasks, product or their experience.
The user should be thanked for their valuable input, given their compensation, and dismissed.