Usability Testing Plans

Preview:

Citation preview

Testing Plans: Mapping the WorkThursday, February 23, 12

You got to know where you want to go.

Thursday, February 23, 12

Thursday, February 23, 12

and you got to know where the pitfalls are.

Thursday, February 23, 12

Thursday, February 23, 12

You need to know

Thursday, February 23, 12

• How

• When

• Where

• Who

• Why

• What

Thursday, February 23, 12

Worries:Formal?Casual?

Thursday, February 23, 12

Prepared.

Thursday, February 23, 12

Test plans also:

Thursday, February 23, 12

Serve as main communication vehicle

Thursday, February 23, 12

Defines requiredresources.

Thursday, February 23, 12

DefineFocal pointsMilestones

Thursday, February 23, 12

Parts of the Test Plan

Thursday, February 23, 12

Purpose, goals, and objectives of the test

Thursday, February 23, 12

Broadly.Major stuff.

Thursday, February 23, 12

Why are you testing?What’s the impetus?

Thursday, February 23, 12

Reasons NOT to test:

Thursday, February 23, 12

Thursday, February 23, 12

• Improving user experience

Thursday, February 23, 12

• Improving user experience

• Everyone else is doing it

Thursday, February 23, 12

• Improving user experience

• Everyone else is doing it

• Space is available

Thursday, February 23, 12

• Improving user experience

• Everyone else is doing it

• Space is available

• Somebody wants to do something shiny

Thursday, February 23, 12

• Improving user experience

• Everyone else is doing it

• Space is available

• Somebody wants to do something shiny

• Market testing

Thursday, February 23, 12

Good reasons to test:

Thursday, February 23, 12

• Understanding which users can use the product well.

• Compensating for acknowledged issues.

• Addressing specific complaints.

Thursday, February 23, 12

Research questions

Thursday, February 23, 12

Clear, succinct

Thursday, February 23, 12

MeasurableQuantifiable

Thursday, February 23, 12

Don’t do this:

Thursday, February 23, 12

Thursday, February 23, 12

• Is the product usable?

Thursday, February 23, 12

• Is the product usable?

• Is the product ready for release or does it need more work?

Thursday, February 23, 12

Thursday, February 23, 12

• How easily do users understand what is clickable?

Thursday, February 23, 12

• How easily do users understand what is clickable?

• How easily do they find X information?

Thursday, February 23, 12

• How easily do users understand what is clickable?

• How easily do they find X information?

• How quickly & successfully do they register for the service?

Thursday, February 23, 12

• How easily do users understand what is clickable?

• How easily do they find X information?

• How quickly & successfully do they register for the service?

• Where in the site do they go to find Search?

Thursday, February 23, 12

Participant characteristics

Thursday, February 23, 12

double-check with client

Thursday, February 23, 12

# of participants

Thursday, February 23, 12

Participant types

Thursday, February 23, 12

Method (test design)

Thursday, February 23, 12

Why?

Thursday, February 23, 12

keeps everyone in the team on the same page

Thursday, February 23, 12

multiple test moderators

Thursday, February 23, 12

focuses test development

Thursday, February 23, 12

protocols

Thursday, February 23, 12

Task list

Thursday, February 23, 12

Thursday, February 23, 12

• Description of task (1 line)

Thursday, February 23, 12

• Description of task (1 line)

• Materials/Machine states required

Thursday, February 23, 12

• Description of task (1 line)

• Materials/Machine states required

• Successful completion criteria

Thursday, February 23, 12

• Description of task (1 line)

• Materials/Machine states required

• Successful completion criteria

• Timing/Benchmarks

Thursday, February 23, 12

Goal:Indirectly expose usability flaws

Thursday, February 23, 12

Prioritize tasks:

FrequencyCriticalityVulnerabilityReadiness

Thursday, February 23, 12

Test environment, equipment, and logistics

Thursday, February 23, 12

Test moderator role

Thursday, February 23, 12

Data to be collectedEvaluation measures

Thursday, February 23, 12

Report contents and presentation

Thursday, February 23, 12

Recommended