Recommending modifications from beta test results

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. After beta testing, five testers report the same confusing Save button. What should you do first?

A Group the similar reports into one issue

B Treat each report as a separate unrelated issue

2. Which issue should be prioritised first?

A A bug that crashes the program for most testers

B A suggestion to change a button colour for one tester

3. Which is a specific recommended change?

A Add a range check so ages outside 0-120 show an error message

B Make the age input better

4. Why should each recommended change link to a requirement?

A It makes the report longer and more detailed

B It shows the change helps the solution meet what it was designed to do

5. Three testers could not find the Export button. Which recommendation links to a requirement?

A Move Export to the main toolbar because one developer likes it there

B Move Export to the main toolbar to meet the requirement that users can export results easily

Match the Pairs

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

Left column		Right column
1Priority: High - app crashes when Save is clicked		AIssue 2: Export option hard to find (reported by testers 1, 3 and 5)
2Recommended change: add a Cancel button to the Settings screen (Requirement 4: users can undo actions)		BA specific modification that fixes an issue and links back to a requirement of the solution
3Grouping similar issues: three testers reported they could not find the Export option, so they are recorded as one issue		CAn issue ranked as urgent because it stops users from completing a core task, so it is fixed first
4A recommendation must be specific and linked to a requirement, not a vague idea		DThe recommendation is vague. It does not say which issue it fixes, what specific change to make, or which requirement it links to.
5Recommendation: Improve the app.		EThe priorities are in the wrong order. A low-impact cosmetic issue is placed before a high-impact issue that stops all users from logging in.
6Fix first: button colour is slightly different on the Help page (Low impact). Fix later: login fails for every user (High impact).		FChange: rename the Go button to Submit Order. Links to Requirement 2: users can place an order easily.

Definitions

recommend modifications

Fill in the Blanks

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

impact = {"crash": 3, "colour": 1} worst = ___(impact, key=impact.get)

reports = ["login", "login", "colour"] count = reports._____("login")

fix = {"change": "Add hint", "req": "R3"} print("Link to requirement:", ___["req"])

for name, score in impact.items(): if score __ 3: print("High priority:", name)

reqs = {"login": "R1", "colour": "R4"} issue = "login" print(issue, "->", reqs.___(issue))

Spot the Error

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

Question 1

A bugs = ["lag", "lag", "typo"]

B g = {}

C for b in bugs:

D g[b] = g.get(b, 0) - 1

Question 2

A imp = {"crash": 1, "typo": 3}

B top = max(imp, key=imp.get)

C print("Fix first:", top)

Question 3

A issue = "Text too small"

B impact = "high"

C change = "Improve the text"

D print(issue, change)

Question 4

A issue = "Search takes 9 s"

B req = "R5: Logo is blue"

C change = "Add a search index"

D print(issue, req, change)

Question 5

A if core and users < 3:

B priority = "high"

C else:

D priority = "low"

Answer Key

Recommending modifications from beta test results

Section A: Quick Questions

A — Group the similar reports into one issue

A — A bug that crashes the program for most testers

A — Add a range check so ages outside 0-120 show an error message

B — It shows the change helps the solution meet what it was designed to do

B — Move Export to the main toolbar to meet the requirement that users can export results easily

Section B: Match the Pairs

Priority: High - app crashes when Save is clicked → An issue ranked as urgent because it stops users from completing a core task, so it is fixed first

Recommended change: add a Cancel button to the Settings screen (Requirement 4: users can undo actions) → A specific modification that fixes an issue and links back to a requirement of the solution

Grouping similar issues: three testers reported they could not find the Export option, so they are recorded as one issue → Issue 2: Export option hard to find (reported by testers 1, 3 and 5)

A recommendation must be specific and linked to a requirement, not a vague idea → Change: rename the Go button to Submit Order. Links to Requirement 2: users can place an order easily.

Recommendation: Improve the app. → The recommendation is vague. It does not say which issue it fixes, what specific change to make, or which requirement it links to.

Fix first: button colour is slightly different on the Help page (Low impact). Fix later: login fails for every user (High impact). → The priorities are in the wrong order. A low-impact cosmetic issue is placed before a high-impact issue that stops all users from logging in.

Section C: Definitions

recommend modifications — Group similar beta test issues, rank them by impact, then suggest a specific change for each one that links back to a requirement of the solution.

Section D: Fill in the Blanks

impact = {"crash": 3, "colour": 1}
worst = max(impact, key=impact.get)

reports = ["login", "login", "colour"]
count = reports.count("login")

fix = {"change": "Add hint", "req": "R3"}
print("Link to requirement:", fix["req"])

for name, score in impact.items():
    if score >= 3:
        print("High priority:", name)

reqs = {"login": "R1", "colour": "R4"}
issue = "login"
print(issue, "->", reqs.get(issue))

Section E: Spot the Error

D — Grouping similar issues means counting how many testers reported each one. The count must go up by 1 each time (+ 1), not down (- 1).

A — The impact scores are reversed. A crash stops users completing tasks, so it must have the higher impact (3) and a typo the lower (1). Otherwise the typo gets prioritised first.

C — A recommended change must be specific and actionable. 'Improve the text' is vague. It should state exactly what to change, such as 'Use 16pt font'.

B — Each recommended change must link to the requirement the issue breaks. The slow search issue relates to the search speed requirement (R3), not an unrelated requirement about the logo colour.

A — An issue that affects a core feature and is reported by many testers should be high priority. The test must be users > 3, not users < 3, which rewards issues reported by few testers.