Observing a beta testing scenario

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. During a beta test scenario, a tester gets stuck on the login screen. What should the observer do?

A Stay quiet, watch and note where they get stuck

B Point to the correct button so they can continue

2. Which observation note is most useful to record?

A Paused for 20 seconds on the Save screen, then clicked Cancel by mistake

B The tester seemed fine

3. A tester pauses for a long time before clicking a button. How should the observer treat this?

A Note the hesitation as a possible usability problem

B Ignore it because the tester did not make an error

4. Which is the correct way to observe a beta testing scenario?

A Explain each step first, then watch them follow your instructions

B Let the tester work through the scenario on their own while you watch

5. A tester clicks the wrong menu item and then goes back. What should be written in the observation notes?

A Say nothing because they fixed it themselves

B Record the error, where it happened and how they recovered

Match the Pairs

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

Left column		Right column
1observe without helping		Aif tester_stuck: log_note('stuck at step 3')
2note: hesitated 12s at Submit		BThe observer gives the tester a hint. Helping hides the real problem and ruins the test, so the observer should stay quiet and write a note.
3Do not interrupt: if a tester is stuck, stay quiet and record what happens instead of giving a hint.		CAn observation note recording a pause, which suggests the control or label was unclear to the tester.
4Observation notes record each step with its outcome: success, hesitation or error.		Dnotes.append((step, 'error'))
5if tester_stuck: print('Click the blue button')		EThe note is vague. It does not record the step, any hesitation or errors, so no usability problems can be identified from it.
6notes = ['Test went fine']		FWatch testers work through the scenario without giving hints, so you see how real users cope on their own.

Definitions

observe without helping

Fill in the Blanks

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

notes = [] notes.______("T1 hesitated at login")

errors = 2 if errors _ 0: print("Usability problem found")

hesitations = 0 hesitations __ 1

helped = False if ___ helped: print("Valid observation")

___ log_note(tester, note): print(tester, ":", note)

Spot the Error

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

Question 1

A helping = True

B hesitated = True

C if not helping:

D print("Keep observing")

Question 2

A notes = []

B seconds_paused = 8

C if seconds_paused > 5

D notes.append("Hesitated")

Question 3

A steps = ["Login", "Pay"]

B for step in steps:

C print("Tell tester:", step)

Question 4

A observer_notes = []

B note = "Missed Save button"

C observer_notes.add(note)

Question 5

A notes = []

B notes.append("Hesitated")

C notes.append("Wrong button")

D print(len(note), "notes")

Answer Key

Observing a beta testing scenario

Section A: Quick Questions

A — Stay quiet, watch and note where they get stuck

A — Paused for 20 seconds on the Save screen, then clicked Cancel by mistake

A — Note the hesitation as a possible usability problem

B — Let the tester work through the scenario on their own while you watch

B — Record the error, where it happened and how they recovered

Section B: Match the Pairs

observe without helping → Watch testers work through the scenario without giving hints, so you see how real users cope on their own.

note: hesitated 12s at Submit → An observation note recording a pause, which suggests the control or label was unclear to the tester.

Do not interrupt: if a tester is stuck, stay quiet and record what happens instead of giving a hint. → if tester_stuck: log_note('stuck at step 3')

Observation notes record each step with its outcome: success, hesitation or error. → notes.append((step, 'error'))

if tester_stuck: print('Click the blue button') → The observer gives the tester a hint. Helping hides the real problem and ruins the test, so the observer should stay quiet and write a note.

notes = ['Test went fine'] → The note is vague. It does not record the step, any hesitation or errors, so no usability problems can be identified from it.

Section C: Definitions

observe without helping — Watch testers complete a scenario without helping them, and note where they hesitate, make errors or succeed, so you can see real usability problems.

Section D: Fill in the Blanks

notes = []
notes.append("T1 hesitated at login")

errors = 2
if errors > 0:
    print("Usability problem found")

hesitations = 0
hesitations += 1

helped = False
if not helped:
    print("Valid observation")

def log_note(tester, note):
    print(tester, ":", note)

Section E: Spot the Error

A — The observer must not help the tester. Set helping = False so the program keeps observing instead of stepping in.

C — An if statement must end with a colon. It should be: if seconds_paused > 5:

C — The observer should only watch each step, not give instructions to the tester. It should be print("Watching:", step).

C — Lists have no add() method. Use append() to record a new observation note: observer_notes.append(note).

D — The variable is called notes, not note, so this causes a NameError. It should be len(notes).