Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

M 32 Reporting Template

Use the following guidelines to assure that required elements are reported. Use the ones that are relevant for your testing purpose, method and setting.

NOTE: this works as guideline. As mentioned above, not everything mentioned has to be described.
NOTE: this template is meant to be used for reporting all kind of tests.

...

Usability test for Tuubi portal

Usability Report.

Mikko Majander, Simone Scarduzio, Wedha Effendy

Actual submission date:

10.12.2009

Revised version:

10.12.2009 (final)

...

Tasks: Test persons are asked to complete series of question and see how fast he/she can accomplish the task without any of help.

Results in main points
The test persons were able to(usability issues found)

  1. The user is confused by too many SEARCH search functions around the portal (we counted 3) and they all hide a different purpose which is absolutely not clear.
  2. Workspace search: the search results are very near to the searchbox although the user takes a lot of time before recognizing them as the actual results of his search.
  3. Workspace Search: once you tick the checkbox, the subscribe button is hidden.. under another searchbox.
  4. Sidebar of subscribed workspaces has an not a clear criteria on grouping the items. In addition to this, the groups are not graphically well divided. Maybe add some margin-top to the groups?
  5. Assignments tab: the submit/cancel buttons are very distant from the input textbox. This problems becomes bigger and bigger with wider screens because the buttons are floating to the right margin of the page.
  6. Assignemnt tab: when uploading a file as an assignment the system doesn't provide feedback of the uploading going on or being terminated successfully.
  7. Check Assessed assignments: you can't easily understand where's the grade (a number) especially if you are not Finnish: in many other countries there's different conventions (letters, different scales of numeric marks, etc.). There's nothing that says that number IS your grade. Especially because there's not a scale. Eg. 3/5.
  8. The column of grades in the table that summarizes your assignments has no title! The meaning of that number (grade) is more and more difficult to understand.
  9. The mark is visible just in the summary of submitted assignments and the teacher's comments are visible just if you click on your grade. Grade and comment should be displayed contextually at least after you click on your mark.
  10. Fancy Ajax calls don't take in consideration to handle the "back" button of the browser. Typical scenario:

...

  • State the objectives for the test and any areas of specific interest
    • Functions and components with which the user directly and indirectly interacted
    • Reason for focusing on a product subset

Method

Participants
Three

...

test users: a full-time university student of Arcada (has been using student portal but no Tuubi) ;

...

an exchange student of IT in Metropolia (uses Tuubi just to check announcements and exam dates);

...

another exchange student of IT in Metropolia with very good knowledge of Tuubi and better overally computer skills.
.h4 Key characteristics and capabilities of user group

...


Users of the Tuubi portal by students' perspective. Fairly good computer skills.

How participants were selected

...

Users were selected from the target user group as representative of new, basic and experienced user.

...

Our three test users were well representing the population because of their different experience

...

about the software, but at the same time they belong to the real population of the software tested.

Context of Product Use in the Test

...

<TODO>

...

Tasks (criteria of acceptance of each task is shown between brackets).

1. Subscribe to "Usability testing" workspace in Tuubi.
(User has the workspace on his/her General-workpsaces)

2. Go to workspace "Usability testing" and read the description from the frontpage of workspace.
(User finds and can open the description)

3. Find and download file named "Usability_document.doc" and open it on the test computer.
(user is reading the content of the file on the computer)

4. Open assignment "Usability testing 1" and do as you have been told in the assigment (in the assignment test person will be asked to upload a file from the desktop as submitting an assignment)
(user has given his/her answer by submitting a file)

5. Open assignment "Usability testing 2" and do as you have been told in the assigment (in the assignment test person will be asked to give feedback about the assignment as a text)
(user has given his/her answer by submitting text)

6. Read feedback for the assigment
(user sees the grade and comment on his/her assignment)

7. Look up the date for the final assignment from calendar
(tells us the day, month, year and time in which the assignment is due to.)

8. See who else is subscribed to this workspace.
(can see other members of this worspace and tells us what role is himself belonging to)

9. Reply to a message on the discussion board.
(There is a reply from user to Test-message)

...

Describe the task scenarios for testing

...

These task represent a selection of most common operations for a student. Principal features of the portal were covered, at least within the perspective of a student who approaches Tuubi as a communication media for university courses.
These tasks were created, chosen, pilot-tested by the organizers of the test.Each partecipant has been introduced to the test environment by a preliminary speech. During this phase we assured to communicate a positive and relaxed mood.

Test Facility Location

Test Facility
Location: Hoas apartments, Leppävaara. Clean study desk with comfortable amount of light and silent surroundings.

...

Software: Windows XP SP3, Internet Explorer 8. MS Word 2003.Test Administrator Tools (report if relevant for the particular test)

  • If a questionnaire was used, describe or specify it here (add these to appendix)
  • Describe any hardware or software used to control the test or to record data (audio, video)

Experimental Design

  • Define independent variables and control variables
  • Describe the measures for which data were recorded (the scale/scope of the recorded data, if relevant for the particular test, i.e., written notes, think aloud in audio recording, etc.).

Procedure

  • Operational definitions of measures (e.g., how is it decided that that a task is completed)
  • Policies and procedures for interaction between tester(s) and subjects (e.g., is the test conductor aloud to answer questions of the user, provide help, etc.)
  • State used: non-disclosure agreements, form completion, warm-ups, pre-task training, and debriefing
  • Specific steps followed to execute the test sessions and record data
  • Number and roles of people who interacted with the participants during the test session
  • Specify if other individuals were present in the test environment
  • State whether participants were paid

Procedure

The test-user has been instructed with an introductive speech Participant General Instructions with an introductive speech the test user has been instructed to think aloud for all the duration of his/her contribution to our test.
A printed task list has been provided before starting in a form of  of per-task numbered list. User has also been asked invited to read it the whole list through and to ask any text comprehension related questions before the test start.
Another printed task list was in hand of the tester, this one complete of the satisfaction criteria.

Test has been handled in two people: a "blabber" and a "scribbler":

The blabber
  • Does the introduction speech
  • Relates to user's question: clearly before test starts and evasively during the test, to keep the observation unobtrusive.
  • Decides and communicates to user and scribbler when the satisfaction criteria were achieved for each task.
The scribbler
  • Positioned behind the test-user, silent and discreet in order to minimize the uncomfortable feeling of being observed
  • Takes note of significant happenings, impressions, behaviors and comments of the user during the test.
  • Takes per-task timings with chronometer.

Participants of this tests were paid back with huge smiles.

Results

Results are mainly qualitative. For someone who is familiar with Tuubi there is no problems completing the tasks easily. That does not mean that Tuubi is good as it is, but that you can learn to master it. One open question is, how steep is the learning curve in Tuubi.

...