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 | |
|---|---|---|
| 1beta testing | Atesters = ['Year 10 student', 'teacher', 'parent'] | |
| 2alpha testing | Bresults = {'meets_requirements': True, 'usable': True} | |
| 3Beta testers should be potential users of the solution, not the developers who built it | CBeta testing happens late, once the solution is near-finished, because users need something working to try. | |
| 4Beta testing checks the solution meets its requirements and is usable | DTesting done by the developers or the development team before the solution is released to potential users | |
| 5Beta testing is done by the developers on their own computers before anyone else sees the solution. | EPotential users try the near-finished solution to check it meets requirements and is usable | |
| 6Beta testing happens at the start of a project, before any code has been written. | FThis describes alpha testing. Beta testing is done by potential users, not the developers. |
Complete each line of code by filling in the missing parts.
Shade in the letter of the line that contains an error.
beta testing — Testing where potential users try the near-finished solution to check it meets requirements and is usable. It follows alpha testing, which is done by the developers.def betatest(solution, testers):stages = ["alpha", "beta", "release"]stage = "alpha" if developer else "beta"passed = all(results)if not completed:
issues.append(task)