Techniques for Testing - User Testing

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. Does user testing involve real users trying a solution?

A True

B False

2. Can user testing help identify usability issues before release?

A Yes

B No

3. Do observers often record points of confusion during testing?

A False

B True

4. Should feedback from user testing be used to guide improvements?

A Yes

B No

5. Does user testing require thousands of participants to be useful?

A True

B False

Match the Pairs

Draw a line connecting each item on the left to its match on the right.

Left column		Right column
1Real users try a solution and give feedback on their experience		AObservers should watch and record what happens during testing
2A moment where a user hesitates or doesn't understand a step		BPoint of confusion
3A technique used to find usability issues before release		CTime taken
4How long it takes a user to complete a given task		DFeedback from user testing should be used to guide improvements
5The team ran a testing session but ignored all the feedback collected		EUser testing
6A user testing session was run with no observer watching or recording		FUser testing

Definitions

User testing

Fill in the Blanks

Complete each line of code by filling in the missing parts.

1. _____ completed 2. Points of confusion 3. Time taken

1. Tasks completed 2. Points of _________ 3. Time taken

1. Tasks completed 2. Points of confusion 3. ____ taken

User testing involves real _____ trying a solution

Feedback from testing guides ____________

Spot the Error

Shade in the letter of the line that contains an error.

Question 1

A User testing involves real users trying a solution.

B It helps identify usability issues before release.

C User testing can only be done after a solution is finished.

D Observers often watch what users do during testing.

Question 2

A Observers record what users struggle with.

B This helps identify confusing parts of a solution.

C Observers should never take notes during a session.

D Notes can be reviewed to plan improvements.

Question 3

A Tasks given to users should always be kept secret from the design team.

B Users are given tasks to complete during testing.

C This shows how easily they can use the solution.

D Task completion time can also be measured.

Question 4

A User testing gathers feedback from real people.

B Feedback from user testing is always ignored.

C This feedback can reveal usability problems.

D Improvements can be made based on this feedback.

Question 5

A A point of confusion shows where a user got stuck.

B This can reveal unclear instructions or design.

C Points of confusion are only recorded by the user themselves.

D Fixing these points can improve the final solution.

Answer Key

Techniques for Testing - User Testing

Section A: Quick Questions

A — True

A — Yes

B — True

A — Yes

B — False

Section B: Match the Pairs

Real users try a solution and give feedback on their experience → User testing

A moment where a user hesitates or doesn't understand a step → Point of confusion

A technique used to find usability issues before release → User testing

How long it takes a user to complete a given task → Time taken

The team ran a testing session but ignored all the feedback collected → Feedback from user testing should be used to guide improvements

A user testing session was run with no observer watching or recording → Observers should watch and record what happens during testing

Section C: Definitions

User testing — A testing technique where real users try a solution and give feedback, helping identify usability issues before release

Section D: Fill in the Blanks

1. Tasks completed
2. Points of confusion
3. Time taken

1. Tasks completed
2. Points of confusion
3. Time taken

1. Tasks completed
2. Points of confusion
3. Time taken

User testing involves real users
 trying a solution

Feedback from testing guides improvements

Section E: Spot the Error

C — User testing can be done at various stages, including on early prototypes, not only after a solution is finished.

C — Observers should take notes during a session to accurately capture what users struggle with.

A — Tasks used in testing should be shared with the design team, since they help interpret the results.

B — Feedback from user testing should inform improvements, not be ignored.

C — Points of confusion are typically recorded by an observer watching the session, not only by the user.