Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column
width65%

Status

USER TESTING NEEDEDUser Testing Needed

Summary

High-level summary to be added after testing has been completed.

Notes

Goals

Excerpt

This test should discover:

  • How easy or difficult is it for the user to reorder an image (using mouse and keyboard)
    • in middle of the list
    • at the end of the list
    • at the beginning of the list
  • Does the mouse 'drag and drop' behaviour work as the user expects?
    • Visual cues for drop targets (position, valid/invalid targets)
      • Does the outline around the image that the mouse is over signify to the user that that's the one they can move at the moment?
    • Red Bar Visual Cue:
      • Is the red bar visual cue meaningful to the user?  Do they know what it means?
      • Does the red bar cause any confusion when the user sees it appear near both the right edge of the (left image) and the left edge of the (right image)?
      • Should the red bar instead just appear in the middle of the two images?
  • Does the keyboard behaviour (and choice of keystrokes) work as the user expects?
    • Is the user able to move the image to the location they want with the keyboard?
    • Is there confusion on Macs between Ctrl key and Apple key?
    • Is the outline around the image helpful as the user arrow keys through to indicate that is the current image the user can move?
  • Affordances for Mouse and Keyboard input. Are the affordances (mouse cursor changes, on-screen instructions) enough to inform the user of the re-ordering functionality? Do they know how to use it?
  • Front-end/Back-end relationship:
    •  Does the relationship between the interface and the backend (i.e. saving state) do what the user expects?

Success Criteria

A successful design has been achieved when:

Protocol

Method and test coordinator script.

Users

Generally speaking we want to user test a wide range of faculty and student users, including people who only use keyboards for navigation (determine accessibility of design).

http://wiki.fluidproject.org/display/fluid/Lightbox+Personas

  • Eileen "Resourceful Adapter"
  • Amanda "Overwhelmed Adopter"

How many users to test? Neilson suggests that testing 5 users, with a minimum of 3 from each user group, within an iterative design process should be sufficient to find most usability issues.

Interaction Design

Underlying design patterns and description of component behavior.

Test Environment

Location and version of the environment that was used. Attach a screenshot of the environment at the time of testing if the environment will change over time.

Results

Full notes and analysis of the user tests.

Image Reoderer User Testing - Round 1 Results

Excerpt Include
Infusion13:Image Reoderer User Testing - Round 1 Results
Infusion13:Image Reoderer User Testing - Round 1 Results
nopaneltrue

More...

Column
width35%
Panel
borderColor#321137
bgColor#fff
titleBGColor#c1b7c3
titleMORE ON USER TESTING
borderStylesolid
Recently Updated
fluid
fluid
labelsuser_testing
Panel
borderColor#93BB6F
bgColor#F8F8F8
titleBGColor#D3E3C4
titleMORE ON IMAGE REORDERER
borderStylesolid
Recently Updated
fluid
fluid
labelsimage_reorderer, lightbox