2.3.2 Testing

Question 1

Testing

Answer 1

“Assessing the performance and functionality of a program under various conditions to make sure it works. Programmers need to consider all the devices the program could be used on and what might cause it to crash.”

Question 2

Iterative testing

Answer 2

“Each module of a program is tested as it is developed.”

Question 3

Syntax error

Answer 3

“Rules of the language have been broken, so the program will not run. Variables not being declared before use. Incompatible variable types (e.g., sum = A); using assignments incorrectly (e.g., 2 + 2 = x); keywords misspelt (e.g., PRNT(“Hello”)).”

Question 4

Logical error

Answer 4

“The program runs but does not give the expected output. Division by zero. Infinite loop. Memory full. File not found.”

Question 5

Test data

Answer 5

“Values used to test a program – normal, boundary and erroneous.”

Question 6

Test data: Normal

Answer 6

“Data supplied to a program that is expected. Using a program written to average student test scores as an example, if allowed scores are 0 – 100, normal test data would include all the numbers within that range.”

Question 7

Test data: Boundary

Answer 7

“Data supplied to a program designed to test the boundaries of a problem. Using a program written to average student test scores as an example, if allowed scores are 0 – 100, boundary test data could be -1, 0, 1, 99, 100 and 101.”

Question 8

Test data: Invalid

Answer 8

“Data of the correct type but outside accepted validation limits. Using a program written to average student test scores as an example, if allowed scores are 0 – 100, invalid test data could be -5, 150, etc.”

Question 9

Test data: Erroneous

Answer 9

“Data of the incorrect type that should be rejected. Using a program written to average student test scores as an example, if allowed scores are 0 – 100, erroneous data might be the string “hello”, the real number 3.725, etc.”