Writing a beta test scenario

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. Which is a better beta test scenario task description?

A Test the app

B Register a new account, log in and add a book to your reading list

2. Which expected outcome is written clearly enough to check?

A The book appears in the reading list and the count shows 1 item

B The app works well

3. Which set of steps belongs in a beta test scenario?

A 1. Open the app 2. Tap Add Book 3. Enter a title 4. Tap Save

B Try adding a book somehow

4. What are the three parts of a beta test scenario in this module?

A Task description, source code, programmer's name

B Task description, steps, expected outcome

5. Which scenario is realistic for a beta tester?

A Search for a book by author and open its details page

B Change the database table structure

Match the Pairs

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

Left column		Right column
1Task: Add a new book to the library catalogue		AThere is no expected outcome, and the steps just repeat the task instead of listing each action
2Expected outcome: The book appears in the catalogue list		BThe task is vague and the expected outcome is not clear, so the tester cannot tell what to do or what counts as a pass
3The steps list the actions a tester follows in order to complete the task		CA clear result the tester checks against to decide whether the scenario passed or failed
4A test scenario is a realistic task with a clear expected outcome, not a vague instruction		DA task description that tells the tester what realistic goal to achieve with the solution
5Task: Test the app Expected outcome: It works		ESteps: 1. Click Add Book 2. Type the title 3. Click Save
6Task: Pay for an order Steps: 1. Pay for the order		FTask: Book a tutor. Expected outcome: A confirmation message shows the time

Definitions

test scenario

Fill in the Blanks

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

scenario = { "____": "Add a book to the cart", "expected": "Cart shows 1 book"}

scenario = { "_____": ["Search", "Click Add"], "expected": "Cart shows 1 book"}

scenario = { "task": "Add a book to the cart", "________": "Cart shows 1 book"}

steps = ["Open app", "Search", "Add item"] for step in _____: print(step)

passed = actual __ expected print("Pass" if passed else "Fail")

Spot the Error

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

Question 1

A Task: Borrow a library book

B Step 1: Log in as a student

C Step 2: Edit the loans table

D Expected: Book is in My Loans

Question 2

A Task: Reset my password

B Step 1: Tap Forgot password

C Step 2: Enter my email address

D Expected: It works well

Question 3

A Task: Order a lunch online

B Step 1: Use the app a bit

C Step 2: Tap Pay with test card

D Expected: Order number shown

Question 4

A Task: Change my username

B Step 1: Open Settings

C Step 4: Type a new username

D Expected: New name is shown

Question 5

A Task: Submit homework online

B Step 1: Log in as a teacher

C Step 2: Upload my essay file

D Expected: Status is Submitted

Answer Key

Writing a beta test scenario

Section A: Quick Questions

B — Register a new account, log in and add a book to your reading list

A — The book appears in the reading list and the count shows 1 item

A — 1. Open the app 2. Tap Add Book 3. Enter a title 4. Tap Save

B — Task description, steps, expected outcome

A — Search for a book by author and open its details page

Section B: Match the Pairs

Task: Add a new book to the library catalogue → A task description that tells the tester what realistic goal to achieve with the solution

Expected outcome: The book appears in the catalogue list → A clear result the tester checks against to decide whether the scenario passed or failed

The steps list the actions a tester follows in order to complete the task → Steps: 1. Click Add Book 2. Type the title 3. Click Save

A test scenario is a realistic task with a clear expected outcome, not a vague instruction → Task: Book a tutor. Expected outcome: A confirmation message shows the time

Task: Test the app Expected outcome: It works → The task is vague and the expected outcome is not clear, so the tester cannot tell what to do or what counts as a pass

Task: Pay for an order Steps: 1. Pay for the order → There is no expected outcome, and the steps just repeat the task instead of listing each action

Section C: Definitions

test scenario — A realistic task a beta tester performs with the solution, written as a task description, steps to follow and a clear expected outcome to check the result against.

Section D: Fill in the Blanks

scenario = {
    "task": "Add a book to the cart",
    "expected": "Cart shows 1 book"}

scenario = {
    "steps": ["Search", "Click Add"],
    "expected": "Cart shows 1 book"}

scenario = {
    "task": "Add a book to the cart",
    "expected": "Cart shows 1 book"}

steps = ["Open app", "Search", "Add item"]
for step in steps:
    print(step)

passed = actual == expected
print("Pass" if passed else "Fail")

Section E: Spot the Error

C — A tester step must be something a real user does in the solution. Editing a database table is a developer action. It should be 'Step 2: Tap Borrow on a book'.

D — The expected outcome must be specific and checkable. 'It works well' is vague. It should state a clear result, such as 'Expected: Reset email is sent'.

B — A step must be one clear, specific action the tester can follow. 'Use the app a bit' is vague. It should be 'Step 1: Add a wrap to the cart'.

C — Steps must be numbered in order so the tester can follow them. This step skips from 1 to 4. It should be 'Step 2'.

B — The steps must match the task description. The task is a student submitting homework, so the tester should log in as a student, not a teacher.