T8 - Errors and testing

Question 1

A syntax error:

Answer 1

-code written doesn’t conform to the rules of the language
cannot be run until fixed

Question 2

Why do syntax errors display

Answer 2

The compiler doesn’t know how to translate the program into machine code

Question 3

Logical error:

Answer 3

The program will run, but it won’t work as the programmer intended

Question 4

A trace table is useful for:

Answer 4

Determining the purpose of an algorithm
Finding the output of an algorithm
Finding errors in an algorithm

Question 5

To draw a trace table, :

Answer 5

make a column for each variable used, in order
You don’t need to fill in a value for a variable which does not change in a particular row

Question 6

Codes are tested with:

Answer 6

Normal data
Boundary data
Invalid data
Erroneous data

Question 7

Normal data:

Answer 7

5 (checks a single digit), 14 (checks two digits)

Question 8

Boundary data:

Answer 8

1 (checks lowest valid data), 100 (checks highest valid data)

Question 9

Invalid data:

Answer 9

-50 (checks negative numbers), 173 (checks data of the correct type that is invalid), 0 (checks just below lower boundary), 101 (checks just above upper boundary)

Question 10

Erroneous data

Answer 10

“ade”, “#$” (checks data of the wrong type
is rejected)

Question 11

Iterative testing

Answer 11

tests modules and parts of a program as the program is developed

Question 12

The programmer during iterative testing

Answer 12

the programmer will usually test the code with knowledge of how it works

Question 13

iterative testing pro

Answer 13

quicker
less hassle to find errors

Question 14

Final testing

Answer 14

tests the whole program at the end of production

Question 15

final testing aka

Answer 15

terminal testing

Question 16

final testing works

Answer 16

• may be tested by the programmer
• tests entire program = aren’t sure of outputs yet