HCD/Website Testing Process

From Rockalypse

< HCD
Jump to: navigation, search

Contents

Group Plans

Each group should come up with a plan. Link them in from here.

Pre Test

  1. Identify User Types
    1. New - No experience with Fedora.
    2. Experienced - Familiar with Fedora or another Linux distribution.
  2. Goals to achieve during testing
    1. Most common - Determine what in general we want to know.
    2. Specific tasks - Write a script that describes how it should go.
  3. Identify Risks
    1. Human ethics forum - Become certified with the City of Meadville.
    2. Paper Cuts - May cause slight pain.
  4. Create Mock-ups - Paper Prototypes
    1. Multiple mockups - Decide which is best.
    2. Rough look - Don't try to perfect.
  5. Perform Self Testing - Testing on our own group.
    1. Feedback - How to improve the interface?
    2. Improve for final users - Based on group feedback.

Testing

  1. Test mockup with participants
    1. Each group will use 2 or 3 participants
    2. Participant performance will be recorded on video
    3. There will be one person dedicated to
      1. Process controller (tell participants tasks)
      2. Mockup controller (physically manipulate mockup to simulate user actions)
      3. Note-taker (taker of notes)
  2. After each trial review performance
    1. Look at notes and video
    2. Discuss issues and possible solutions
  3. If needed revise mockups and script
  4. Repeat for each participant

Analysis

  1. Video
    1. Compile video from testing and edit in to a short 5-10 minute summary of our testing process and the results obtained. To be shared with fedora community.
  2. Answers
  3. Report
    1. A Short written analysis of your personal experience with the paper prototype testing and your views on the results obtained from the testing.
  4. Final in class report
    1. IRC Conversation to share the results of our testing with the fedora website community.

Group Sketches

Skible

Members: Radu, Will, Genevieve

Testing Process

  1. Collect general user feedback from existing high fidelity mock-ups from Mairin.
  2. Construct single page mock-ups.
  3. Create interaction scripts.
  4. Perform test and collect feedback.
  5. Create website wide mock-ups.
  6. Construct complete website scripts. Site scripts differ from page scripts in that the requests would require the user to find their way through multiple pages in the website. (Ex. Find out more about joining the community.)
  7. Perform site testing.
  8. Record all sessions to later analyze them for hesitation / worry / frustration etc.

To Clear Things Up

  1. General feedback will give us working knowledge for the initial low fidelity mock-ups.
  2. Single page mock-ups are aimed at testing simple elements on particular pages.
  3. The interaction scripts at this point will be succinct and aimed at specific problems.
  4. Feedback collected during this testing phase will be used for website wide mock-ups.

Make sure to get approval for using test subjects from outside the class.

The Matt, Evan, and Jonathan Miller Kauffman, LLP Group

Members: Matt, Evan, Jonathan Miller Kauffman

Pretest

Getting FS Students?

-Entrance Questions - Name, age, gender, internet experience and target audience group.
-What classes would be most suited to our needs?
-Which departments will we draw samples from?
-Will we have a combination of almost computer savvy people and novices?
-Which is more valuable to our testing process?
-Mailing list of Fedora users on campus


Questions to ask Students
-Ask users to suggest tasks that would make things easier?
-What are the top # (3?) tasks you will click on? (from the mock ups)
-How quickly can students do said tasks?


During the test 

-Keep the participants on the task. People will tend to wander off, but it’s important to keep them focused on the task.
-Take shorthand notes or (even better) get someone else to take notes, focusing on really important behaviors.
-Let the participant make mistakes. This will reveal aspects of the interface that may need improvement.
-Answer questions with questions, forcing the user to give more feedback.
-Don’t tell the participant what to do, but you can suggest and discuss design solutions
-Don’t explain the interface. Doing so prevents you from getting their unbiased perception of the site.
-Lead the test subject through a series of questions/tasks, encouraging them to think out loud.


Post test 

-Probably needs to be experimented
-How to digest information?
-Data Analysis?
-Targeting main problems that most users experienced
-Redesign as needed, further testing


Usability site -> http://www.webcredible.co.uk/user-friendly-resources/web-usability/usability-testing.shtml

Moderating the Test ( http://www.digital-web.com/articles/practical_usability_testing/)

Group 4.1

Members: Sam Ross, Jamie Keep, Matt Fody, Eric Hildebrand

1. Create a prototype base – Printed Mock-up 

  a.	Try color Mock-up to test color schemes
  b.	Identify problems from old Mock-ups 
     i.	See what has been changed
     ii.	See what has stayed the same

2. List a change of ideas to test 

  a.	Write on Mock-up
  b.	List on a separate piece of paper

3. Edit and creating new the Mock-ups

4. Get people from community to test it out 

  a.	Suitable testing area for a lot of people
  b.	Ex. Download Button idea’s
     i.	Download
     ii.	Download – Free

5. Summarize live testing 

  a.	Figure out the user issues
  b.	What user feedback on Mock-up/buttons
  c.	Find the challenge the user had with navigation of the page

6. Write up report on issues/summery

7. Create a new Mock-up

8. Repeat Steps 1-7 until satisfied with Mock-up internally

9. If needed present finding to the group as a whole

10. Final Mock-up with group

11. Present Mock-up to designers

12. If needed refurbish Mock-up

Retrieved from "http://wiki.rockalypse.org/HCD/Website_Testing_Process"
Personal tools