Testing

Question 1

If you cannot test everything, what do you test? Explain why.

Answer 1

Test for expected errors.

Valid data
Data that is perfectly acceptable, reasonable and fit to be processed.

Valid but unusual data
Data that should not be rejected even though it seems odd.

Boundary condition data
Data near critical values, called ‘tipping points,’ can trigger code behaviour changes, often causing logical errors in programming.

Wrong data
Data with an inappropriate format would be expected to generate an error.

Absent data
A blank field entry will test how the system handles a ‘no entry’ entry.

Question 2

What is a “testing table”? What does it record?

Answer 2

A testing table documents all steps as a summary table and provides record of evidence for functionality testing.

The table will have columns for: Name of
test, test method and input, expected output, actual output and action taken.