Document Testing Results

1.5 Document the results of testing

Testing Documentation

A Test Plan should be constructed which indicates an incremental development where each module is to be tested in turn, with appropriate test stubs. For each test, expected results should be noted.

A Test Log indicates the results of each test run, whether the test is successful or not. If a test is successful and an error has been discovered then the code should be redesigned, amending pseudocode, recoded and retested.

The advantage of this method is that errors are likely to be localised to the module which is currently under test.

Mod Ref 2 Mod Name: CalcGrade

Test Case Test Data Expected Result Actual Result Comments
1 Exam1=50Exam2=50
Total=100Average=50

Grade=’C’

As expected
n/a
2
Exam1=0Exam2=50 Total=50Average=25

Grade=’No award’

As expected
n/a
3
Exam1=100Exam2=-1 Error message for Exam2
No error message shown.
Calculation carried out with incorrect data
4
Exam1=70Exam2=70 Total=140Average=70

Grade=’A’

As expected
n/a
5
Exam1=60Exam2=50 Total=110Average=65

Grade=’B’

As expected
n/a

Note: n/a is short for not applicable.

Next: Testing Theory