Building a Testing Script
Now that we know what we are looking to accomplish in our
usability test, how do we go about doing it? The answer to this
question lies in first creating a good testing script, or
blueprint. The thought process being that you can use this same
script for every test you give for a particular application in
order to make sure your test results are all as consistent and
uniformed as possible.
Creating a good usability test script can require some thought
and effort. The following are some areas to be aware of while
designing your scripts.
Perhaps the most important thing to consider while creating an
actual testing script for this method of testing that we have
covered is to remember to take advantage of the ability to
record audio. Be sure to encourage the user to think out loud
so that you can capture their thoughts and actions. With this
in mind, you will want to prompt them from time to time to keep
talking and clarifying what actions they are trying to perform.
Along with taking advantage of audio recording, you will want
your scripted task to be clear and direct to the user, but in a
way that it does not give away to much information. It can be a
fine balance in giving testers enough to work with, while
avoiding telling them exactly what to do.
The last, and probably most obvious ingredient in a usability
testing script is the actual questions/tasks you wish the
testers to address. Again, your goal is to keep the test
somewhat informal, and only 20 or 30 minutes in length.
Breaking a testing script up into three key sections can be
helpful. These three sections include: An Introduction, tasks,
and a debriefing. The introduction should help set the stage
for the test. Give the user all of the facts, your name, how
long the test will run, etc. This is also a good time to work
in any legal paperwork such as a consent form of some kind so
that the user is aware that you are collecting their data, how
you will be using that data, and that they give you full
ownership of any data you collect. The tasks is a list of the
specific tasks you want the user to perform, and the debriefing
is kind of a wrap-up that brings closure to the test.
New on the Java Boutique:
New Review:
Time Management Made Easy with the Quartz Enterprise Job Scheduler
Why not just use the Java timer API? This open source scheduling
API boasts simplicity, ease-of-integration, a well-rounded feature
set, and it's free!
New Applet:
Reverse Complement
Reverse Complement is a simple applet that converts DNA or RNA
sequences into three useful formats.
Elsewhere on internet.com:
WebDeveloper Java
Lots of Java information on webdeveloper.com
WDVL Java
Thorough Java resource at the Web Developer's Virtual Library.
ScriptSearch Java
Hundreds of free Java code files to download.
jGuru: Your View of the Java Universe
Customizable portal with online training, FAQs, regular news updates, and tutorials.
