ACARA Digital Technologies Years 9–10 Definitions Worksheet: Testing and Validating Programs (Modules 591–622)
Name:
Date:
Class:
✎
Key terms
Write what each term means, in your own words.
1
test plan
2
test first
3
input()
4
tests = [(5, 25), (0, 0)]
5
for value, expected in tests:
6
round(actual, 2) == expected
7
assert not is_valid(-5)
8
test coverage
9
test report
10
regression testing
Answer Key
ACARA Digital Technologies Years 9–10 · Modules 591–622 · Student wording will vary for definitions
1test plan — A list, made before testing, of normal, boundary and invalid test cases for each requirement, with the expected result for every test.
2test first — Write test cases and expected results from the requirements before coding, so they check what the program should do, not what your code does. Rerun them as it grows.
3input() — Pauses a program so you can type a test value; it returns text. Test by typing each planned input in order, then compare the printed output with the expected result.
4tests = [(5, 25), (0, 0)] — A list of (input, expected) tuples. Each tuple is one test case, so a loop can run many tests stored in one variable. Add a new tuple to add a new test.
5for value, expected in tests: — Loops over each (input, expected) tuple in tests, unpacking it into two variables. Then you call the function, compare actual to expected, and print PASS, or FAIL with both values.
6round(actual, 2) == expected — Floats can be slightly inexact (0.1 + 0.2 is not 0.3), so round the actual result to a set number of decimal places before comparing it with the expected value.
7assert not is_valid(-5) — Tests that bad input is rejected: call the validator with an invalid value and assert it returns False. If an error is expected, use try/except; no error means the test fails.
8test coverage — Test cases are enough when they use normal, boundary and invalid data and run every branch and loop. Missing any leaves the program only partly validated, and passing tests never prove no bugs.
9test report — A summary of how many tests passed and failed, what was fixed and retested, and a conclusion on whether the program is validated, backed by the results and any limitations.
10regression testing — After fixing a bug, rerun the failed test and all earlier tests, because a fix can break code that used to pass.