-
Notifications
You must be signed in to change notification settings - Fork 0
/
Usability Test Plan Template.html
215 lines (208 loc) · 10.4 KB
/
Usability Test Plan Template.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
<!DOCTYPE html>
<!-- saved from url=(0051)https://profs.info.uaic.ro/~stefan.negru/usability/ -->
<html lang="en-us"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="publisher" content="blankdots.com">
<meta name="author" content="Stefan Negru">
<meta name="keywords" content="usabilityTest, template">
<meta name="description" content="usabilityTest Template with microdata">
<meta name="robots" content="noindex,nofollow">
<link rel="stylesheet" type="text/css" href="./Usability Test Plan Template_files/style.css">
<title>Usability Test Plan Template</title>
</head>
<body>
<header>
<h1>Usability Test Plan Template</h1>
<span id="logo"><a href="http://www.w3.org/html/logo/">
<img src="./Usability Test Plan Template_files/html5-badge-h-css3-semantics.png" width="83" height="32" alt="HTML5 Powered with CSS3 / Styling, and Semantics" title="HTML5 Powered with CSS3 / Styling, and Semantics">
</a></span>
</header>
<section>
<h1 class="hidden">Usability Test Plan Section</h1>
<article class="usabilityTest">
<div class="usabilityTestInfo">
<h3>Test Plan for: <span>Twitter Fight</span> <span>Component</span></h3>
<div class="usabilityTestBackground">
<h4>Persona Type Tested: <span>Primary/Secondary/Negative/Served</span></h4>
<h5>Context: <span>the user tested the game at home, at his own pace</span> </h5>
<h5>Duration: <span>15 minutes</span></h5>
<p>Complete the following before starting: <a href="https://profs.info.uaic.ro/~stefan.negru/usability/testingscript.html">Greeting and Consent</a> & <a href="https://profs.info.uaic.ro/~stefan.negru/usability/userbackground.html">User Background Information</a>.</p>
</div>
</div>
<div class="usabilityTestObjectives">
<h5>Overall Objectives</h5>
<p>Quality and Overall Playability of the Game etc.).
</p><ul>
<li>Make sure that the interface is light, yet intuitive, responding to user feedback;</li>
<li>Keep the game simple, yet fun and pleasent;</li>
<li>Have a basic idea of what features can be added or improved upon;</li>
</ul>
</div>
<div class="usabilityTestScenarios">
<h5>Scenario</h5>
<p>Imagine you are looking over what some of your friends did or talked about recently and as you finish you would like to unwind and see what other people they follow. This game is a solution as it arranges famous people your friend follows in a quick list and you can see them as you fight out the match.</a>. </p>
</div>
<div class="usabilityTestDetails">
<div class="detailsLeft">
<h5>Tasks</h5>
<p>Each user will have to go through these task in the estimated time. If they take longer, as this is a game of 1 vs 1 it will not be enjoyable for the other party.</p>
<ul>
<li>Task1-1: Logging in/Interface accomodation + <span>estimated 30-60 seconds.</span>;</li>
<li>Task1-2: Choosing a character + <span>60 seconds</span>;</li>
<li>Task2-1:Setting up the board + <span>limited by timer 60 seconds</span>;</li>
<li>Task2-2:Actual Gameplay + <span>between 5 to 15 minutes</span>;</li>
</ul>
<p>If a user completes a task faster, then it is better to have ideas of designing a ranking system as part of the interface.</p>
<h5>Post-test Questions</h5>
<p>These questions could be presented to the user as a questionnaire or verbally asked.</p>
<ul>
<li>Did you find the game fun? Would you replay it?</li>
<li>What did you think about the interface? Was it to your liking? Did it lack anything?</li>
<li>Was the design easy to comprehend/intuitive? Was it difficult to play?</li>
<li>As many questions needed.</li>
</ul>
</div>
<div class="detailsRight">
<h5>Notes for Test Coordinator</h5>
<ul>
<li>The tasks are all times based. The users basically are monitored as they perform the tasks.;</li>
<li>Read the user the scenario for the test;</li>
<li>The tasks are straight forward. If the user shows sign of confusion, then the interface should be simplified;</li>
<li>Record the user's actions, comments, questions, and body language (write them in the Test Observations section accompanied by video/audio).</li>
</ul>
<h5 id="references">References</h5>
<ul>
<li>Fluid <a href="http://wiki.fluidproject.org/display/fluid/User+Testing">User Testing</a>;</li>
<li><a href="http://www.usability.gov/templates/index.html">usability.gov</a> Templates;</li>
<li><a href="http://www.amazon.com/Handbook-Usability-Testing-Effective-Communications/dp/0471594032">Handbook of Usability Testing</a> by Jeffrey Rubin;</li>
<li><a href="http://www.amazon.com/A-Practical-Guide-Usability-Testing/dp/1841500208">A Practical Guide to Usability Testing</a> by Joseph S. Dumas and Janice C. Redish.</li>
</ul>
</div>
</div>
<div class="otherDetails">
<h5>Other Notes</h5>
<p>Written/video/audio notes done attached to the usability test. These notes reflect the user thoughts and frustrations.</p>
</div>
</article>
<article class="usabilityTestResults">
<div class="usabilityTestResultsInfo">
<h3>Test Results for: Twitter Fight</h3>
<h4>Success Criteria</h4>
<p>A successful design has been achieved when:</p>
<ul>
<li>50% of users have managed to play a game to the end within the time frames allocated above;</li>
<li>80% of users have managed to play a game to the end;</li>
<li>The game complexity has been satisfactory to 50% of the end users;</li>
</ul>
</div>
<div class="usabilityTestResultsInfo">
<h4>Summary</h4>
<p>After the tests the user gave the following feedback</p>
<ul>
<li>3 out of 4 users found that the game is too simple and wanted more complex features;</li>
<li>2 out of 4 users have found the game short, but fun;</li>
<li>3 out of 4 users used in test have enjoyed the interface and likes how simple it is to navigate;</li>
<li>These finding reflect the observation notes of the observer.</li>
</ul>
</div>
<div class="usabilityTestResultsInfo">
<h5>Demographics</h5>
<table class="testTable"><tbody>
<tr>
<th class="testTableTh"> User Number </th>
<th class="testTableTh"> Gender </th>
<th class="testTableTh"> Age Range </th>
<th class="testTableTh"> Persona Type </th>
<th class="testTableTh"> Technical Level </th>
<th class="testTableTh"> Background questions answers </th>
</tr>
<tr>
<td class="testTableTd"> Ashley </td>
<td class="testTableTd"> Female;</td>
<td class="testTableTd"> 22;</td>
<td class="testTableTd"> Primary;</td>
<td class="testTableTd"> IT Field;</td>
<td class="testTableTd"> ??;</td>
</tr>
<tr>
<td class="testTableTd"> Alex </td>
<td class="testTableTd"> Male;</td>
<td class="testTableTd"> 25;</td>
<td class="testTableTd"> Secondary;</td>
<td class="testTableTd"> IT Field;</td>
<td class="testTableTd"> ??;</td>
</tr>
<tr>
<td class="testTableTd"> Teodora </td>
<td class="testTableTd"> Female;</td>
<td class="testTableTd"> 67;</td>
<td class="testTableTd"> Negative;</td>
<td class="testTableTd"> None;</td>
<td class="testTableTd"> ??;</td>
</tr>
<tr>
<td class="testTableTd"> Jennifer </td>
<td class="testTableTd"> Female;</td>
<td class="testTableTd"> 27;</td>
<td class="testTableTd"> Served;</td>
<td class="testTableTd"> General;</td>
<td class="testTableTd"> ??;</td>
</tr>
</tbody></table>
<p>Literature recommends testing no more than <strong>five users</strong> and running as many small tests as you can afford, according <strong> to Nielsen, J. (1994). Usability Engineering, Academic Press Inc, p 165</strong>.</p>
</div>
<div class="usabilityTestResultsInfo">
<h5>Interaction Notes</h5>
<p>Enter a detailed descriptions of the participants' interactions in this table. The table can be separated by task, category, or whatever makes most sense for this test.</p>
<table class="testTable"><tbody>
<tr>
<th class="testTableTh">User</th>
<th class="testTableTh">Task 1</th>
<th class="testTableTh">Task 2</th>
</tr>
<tr>
<td class="testTableTd">Ashley </td>
<td class="testTableTd"> Finished Quickly initial setup + 1 minute</td>
<td class="testTableTd"> Played one game till end + 7 minutes</td>
</tr>
<tr>
<td class="testTableTd">Alex </td>
<td class="testTableTd"> Finished Quickly initial setup + 45 seconds</td>
<td class="testTableTd"> Played one game till end + 8 minutes</td>
</tr>
<tr>
<td class="testTableTd">Teodora </td>
<td class="testTableTd"> Had difficulty understanding + 3 minute</td>
<td class="testTableTd"> Played one game till other participant left + 27 minutes</td>
</tr>
<tr>
<td class="testTableTd">Jennifer </td>
<td class="testTableTd"> Did everything in the time + 1.5 minutes</td>
<td class="testTableTd"> Played one game till end + 7 minutes</td>
</tr>
</tbody></table>
<p>A user might complete a task in a shorter or greater time than the <strong>estimated time</strong>. If the <strong>completion time</strong> exceeds the estimated time then it there is an issue with the design. Also a user might skip the current task thus the <strong>completion time</strong> would be <strong>0</strong>. </p>
</div>
<div class="usabilityTestResultsInfo">
<h5>Post-test Questions Answers</h5>
<p>Before the test write down some expected answers to these questions in order to compare them with the user's answers. Another solution is to establish the expected answers by using a control user.</p>
</div>
<div class="usabilityTestResultsInfo">
<h5>Test Observations</h5>
<p>Written/video/audio notes done attached to the usability test. These notes reflect the user thoughts and frustrations.</p>
</div>
<div class="otherDetails">
<h5>Potential Design Improvements</h5>
<p>Potential design improvements listed here, in a bullet or table format.</p>
<ul>
<li>Improve game interface to look similar to twitter for user to accomodate faster;</li>
<li>Add a dropdown for a way to select from more skilled users;</li>
<li>Add animations to design to make it seem more interactive;</li>
<li>Allow user custumization with colors and themes;</li>
</ul>
</div>
</article>
</section>
<footer id="footer">
<span id="license"><a href="http://creativecommons.org/licenses/by/3.0/"><img alt="Creative Commons License" style="border-width:0" src="./Usability Test Plan Template_files/80x15.png"></a></span>
</footer>
</body></html>