2. Efficiency
2.1 Performance Measurement
2.2 Remote Testing
2.2.1 Overview
Remote usability testing is used when tester(s) are separated in space and/or time from the participants. This means that the tester(s) cannot observe the testing process directly and that the participants are usually not in a formal usability laboratory. There are different types of remote testing. One is same-time but different-place, where the tester can observe the test user’s screen through computer network, and may be able to hear what the test user says during the test through speaker telephone. Another is different-time different-place testing such as journaled sessions, where the user’s test session is guided and logged through a special piece of software as well as additional code added to the system being tested.
2.2.2 Procedure
Tools
- Computer network through which participants can send the test results to the tester
- Application like Look@me that allow the tester to observe the participant’s screen during the test
- Application like Lotus Videocam that can record, and replay the recorded screen series
- Speaker telephone if the participant is supposed to speak aloud or commnunicate with the tester
- Voice recording to record the verbal activities during the test
- Journal software to guide and log the usability test session
2.3 Retrospective Testing
**Overview**
If a videotape has been made of a usability test session, the tester(s) can collect more information by reviewing the videotape together with the user participants and asking them questions regarding their behavior during the test. So this technique should be used along with other techniques, especially those where the interaction between the testers and the participants is restricted. But using this technique means that each test takes at least twice as long. Another obvious requirement for using this technique is that the user’s interaction with the computer needs to be recorded and replayed.
1 | **Procedure** |
Review the recording of the usability test session with the test user. Ask the test user questions and let the test user describe what he/she is doing and why.
