Top Banner
WHY EVERY COMPANY SHOULD ADOPT THE TESTING MANTRA Rene Rebane Senior UX Architect 2013
35

Why Every Company Should Adopt the Testing Mantra

Dec 08, 2014

Download

Design

What is testing all about? Is it just QA or something much-much more? When to test? How to test? Who are the people you should run your tests on? These are just some of the questions answered in the presentation.

This presentation was originally made in August 2013 and presented at the Tallinn Technopolis Ülemiste Business Breakfast event.
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Why Every Company Should Adopt the Testing Mantra

WHY EVERY COMPANY SHOULD ADOPT THE TESTING MANTRA

Rene RebaneSenior UX Architect

2013

Page 2: Why Every Company Should Adopt the Testing Mantra

2013

Today’s topics

• What is usability testing?

• Why to test?

• Good time for testing

• What to test?

• Testing process and hands on

• Cherry.ee example

Page 3: Why Every Company Should Adopt the Testing Mantra

2013

User testing?Never heard of it!

Page 4: Why Every Company Should Adopt the Testing Mantra

2013

What is usability testing?

Page 5: Why Every Company Should Adopt the Testing Mantra

2013

Page 6: Why Every Company Should Adopt the Testing Mantra

2013

Observing the user while they use the webpage, product or

service through tasks you have given them.

Page 7: Why Every Company Should Adopt the Testing Mantra

2013

Why to test?

Page 8: Why Every Company Should Adopt the Testing Mantra

2013

“If you want a great site, you’ve got to test. After you’ve worked on a site for even a few weeks, you can’t see it freshly anymore. You know too much. The only way to find out if it really works is to test it.”

– Steve Krug, Don’t Make Me Think

Page 9: Why Every Company Should Adopt the Testing Mantra

2013

Why to test?

• Find out usability problems

• Why products, services and websites fail

• Understand how users think

• Risk reduction

• No surprises

Page 10: Why Every Company Should Adopt the Testing Mantra

2013

Does not help to answer

• Do people like it

• Will people buy it

• How people will use it mostly

• What kind of people will use it

• What solution is better A or B

Page 11: Why Every Company Should Adopt the Testing Mantra

2013

Good time for testing

Page 12: Why Every Company Should Adopt the Testing Mantra

2013

Beginning of the project End of the project

Possibility of changes

Page 13: Why Every Company Should Adopt the Testing Mantra

2013

Beginning of the project End of the project

Cost of changes

Page 14: Why Every Company Should Adopt the Testing Mantra

2013

What to test?

Page 15: Why Every Company Should Adopt the Testing Mantra

2013

Page 16: Why Every Company Should Adopt the Testing Mantra

2013

Page 17: Why Every Company Should Adopt the Testing Mantra

2013

Page 18: Why Every Company Should Adopt the Testing Mantra

2013

Page 19: Why Every Company Should Adopt the Testing Mantra

2013

Page 20: Why Every Company Should Adopt the Testing Mantra

2013

Page 21: Why Every Company Should Adopt the Testing Mantra

2013

Testing process

Page 22: Why Every Company Should Adopt the Testing Mantra

2013

Set goals and red routes

Prepare tasks

Prepare object, service or website

Gather people

Test session

Analysis & report

Page 23: Why Every Company Should Adopt the Testing Mantra

2013

Where to find people?

Page 24: Why Every Company Should Adopt the Testing Mantra

2013

Where to find people?

• Friends and acquaintances

• Coffee shops

• Shopping centres

• Streets

• Amongst clients

Page 25: Why Every Company Should Adopt the Testing Mantra

2013

0

How many tests to conduct?

3 6 9 12 150%

50%

100%

75%

25%

Page 26: Why Every Company Should Adopt the Testing Mantra

2013

One test with 8 usersFirst test with 8 users Found 5 problems

Page 27: Why Every Company Should Adopt the Testing Mantra

2013

Two test with 3 usersFirst test with 3 users Second test with 3 users Found 9 problems

Page 28: Why Every Company Should Adopt the Testing Mantra

2013

How to analyze?

Page 29: Why Every Company Should Adopt the Testing Mantra

2013

How to analyze?

• Write down what happened

• Why it is unexpected

• Why it is bad (longer process, wrong element usage)

• Remember it is not statistics

Page 30: Why Every Company Should Adopt the Testing Mantra

2013

Does problem occur on a red route?

Is the problem difficult to

overcome?

Is the problem

persistent?low

Is the problem difficult to

overcome?

Is the problem

persistent?

Is the problem

persistent?

Medium

Serious

Critical

Page 31: Why Every Company Should Adopt the Testing Mantra

2013

Next steps

• What to keep

• What to change

• What to test more

• What to measure later

Page 32: Why Every Company Should Adopt the Testing Mantra

2013

Let’s try it

Page 33: Why Every Company Should Adopt the Testing Mantra

2013

Cherry.ee case

Page 34: Why Every Company Should Adopt the Testing Mantra

2013

Q & A