...
• The goal of the test: what do you want to achieve?
We wan't to learn what development needs exists to make using Tuubi more practical and find missing functions. What I try to explain is: The basic functions of Tuubi are probably pretty much fine, but what should be changed or developed
• Where and when will the test take place?
Test will be take place at lab-room some time there is no class in session.
• How long is each test session expected to take?
20 minutes.
• What computer support will be needed for the test?
No computer support will be need. If test is conducted on a OS that is not familiar with the test person, a briefing of the common features will be given and necessary programs will be started.
• What software needs to be ready for the test?
Web browser, word processor, text editor, program to open PDF-files.
• What should the state of the system be at the start of the test?
User has been logged to Tuubi (with testers account so that we know what to expect).
• What should the system/network load and What should the system/network load and response times be? (not too fast or too slow);
• Who will serve as experimenters for the test?
• Who are the users going to be and how are we going to get hold of them?
• How many users are needed?
• What test tasks will the users be asked to perform?
• What criteria will be used to determine when the users have finished each of the test tasks correctly?
• What user aids will be made available to the test users (manuals, online help, etc)?
• To what extend will the experimenter be allowed to help the users during the test?
• What data is going to be collected and how will it be analysed?