Constructing a beta testing plan

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. Which of these is a core part of a beta testing plan?

A A list of the features that will be tested

B The full source code of the program

2. Who should the testers in a beta testing plan be?

A Only the developers who wrote the code

B Representative end users, who did not build the software

3. A beta testing plan says: 'Testing runs from 3 to 14 June, with feedback due by 17 June.' Which element is this?

A The schedule

B The features to test

4. Which is the best way to plan how results are collected?

A Give every tester the same feedback form or survey

B Ask testers to remember problems and tell you later

5. Which statement about a beta testing plan is correct?

A It only states the date the software will be released

B It states what is tested, who tests, when, and how results are recorded

Match the Pairs

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

Left column		Right column
1Features to test: login, search, checkout		AResults: online survey and bug report table
2Testers: 10 students from Year 11 Maths		BIdentifies who will do the beta testing, so the plan says how many testers and what type of users they are
3The schedule states when beta testing starts and finishes so it fits within the project time frame		CThe plan does not list specific features to test and does not state who the testers are or how they were selected.
4The plan states how results will be collected and recorded, such as a feedback form filled in by each tester		DNames the core features that testers will try, so the plan covers the parts of the program that matter most
5Plan: Test the whole app. Testers: anyone.		ESchedule: 3 to 14 June, results due 17 June
6Schedule: test sometime. Results: remember feedback.		FThere are no dates in the schedule and no method for recording results, so feedback may be lost.

Definitions

beta testing plan

Fill in the Blanks

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

features = ["login", "search"] print(len(________))

testers = ["Mia", "Jack", "Zoe"] print(___(testers))

start = "1 March" end = "14 March" print(start, ___)

results = [] results.______("Login: pass") print(results)

plan = {"testers": 5, "when": "May"} for part __ plan: print(part)

Spot the Error

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

Question 1

A features = ["login", "cart"]

B testers = ["Ava", "Liam"

C for f in features:

D print("Test", f)

Question 2

A plan = {}

B plan["start"] = "2026-03-02"

C plan["end"] == "2026-03-16"

D print(plan)

Question 3

A testers = ["Ava", "Mia"]

B count = length(testers)

C print("Testers:", count)

Question 4

A results = []

B name = input("Tester name: ")

C bug = input("Bug found: ")

D results.add([name, bug])

Question 5

A f = open("results.txt", "a")

B line = "login,pass,Ava"

C f.write[line]

D f.close()

Answer Key

Constructing a beta testing plan

Section A: Quick Questions

A — A list of the features that will be tested

B — Representative end users, who did not build the software

A — The schedule

A — Give every tester the same feedback form or survey

B — It states what is tested, who tests, when, and how results are recorded

Section B: Match the Pairs

Features to test: login, search, checkout → Names the core features that testers will try, so the plan covers the parts of the program that matter most

Testers: 10 students from Year 11 Maths → Identifies who will do the beta testing, so the plan says how many testers and what type of users they are

The schedule states when beta testing starts and finishes so it fits within the project time frame → Schedule: 3 to 14 June, results due 17 June

The plan states how results will be collected and recorded, such as a feedback form filled in by each tester → Results: online survey and bug report table

Plan: Test the whole app. Testers: anyone. → The plan does not list specific features to test and does not state who the testers are or how they were selected.

Schedule: test sometime. Results: remember feedback. → There are no dates in the schedule and no method for recording results, so feedback may be lost.

Section C: Definitions

beta testing plan — A plan that states which features will be tested, who the testers are, when testing happens and how the results are collected and recorded.

Section D: Fill in the Blanks

features = ["login", "search"]
print(len(features))

testers = ["Mia", "Jack", "Zoe"]
print(len(testers))

start = "1 March"
end = "14 March"
print(start, end)

results = []
results.append("Login: pass")
print(results)

plan = {"testers": 5, "when": "May"}
for part in plan:
    print(part)

Section E: Spot the Error

B — The list of testers is missing its closing square bracket. It should be testers = ["Ava", "Liam"].

C — == compares values, so this does not store the end date in the schedule. It would also raise a KeyError. Use = to assign: plan["end"] = "2026-03-16".

B — Python has no length() function. Use len(testers) to count how many testers are in the plan.

D — Lists do not have an add() method. Use results.append([name, bug]) to collect each tester's result.

C — write is a method, so it must be called with round brackets. It should be f.write(line) to record the result in the file.