Tip: Choose Save as PDF in the print dialog to download. Use A4 paper size.
Shade in the A or B circle for each question.
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 1alpha testing | Astages = ["alpha", "beta", "release"] | |
| 2assert calculate_total(2, 5) == 10 | Btester = "developer" | |
| 3Alpha testing is developer-run: the person who wrote the code tests it against the requirements | CThe order is wrong. Alpha testing comes before beta testing, so errors are found and fixed before users test the solution. | |
| 4Alpha testing happens before beta testing, so the next stage only starts once errors are fixed | DAlpha testing is run by the developer during development, not by end users. Users take part in beta testing. | |
| 5tester = "end user" # alpha testing | ETesting run by the developer during development to check the solution meets requirements and works correctly | |
| 6stages = ["beta", "alpha", "release"] | FAn alpha test the developer runs to check a function gives the expected output so any error can be found and fixed |
Complete each line of code by filling in the missing parts.
Shade in the letter of the line that contains an error.
alpha testing — Testing run by the developer during development to check the solution meets requirements and works correctly, so errors are found and fixed before beta testing with users.assert calc_total(2, 5) == 10def test_total():
assert total([2, 3]) == 5stages = ["alpha", "beta"]
print(stages[0])expected = 10
if run_test(5) != expected:
print("Error found - fix it")tests = [(2, 4), (3, 6), (0, 0)]
for inp, expected in tests:
assert double(inp) == expected