Planning: Testing Making your program ‘crash proof’

Purpose Ensures that each separate part of a program works as expected. – Functions() and Procedures() Ensures that when combined all parts work as expected: – They receive the correct parameters and return the correct data Makes the development cycle more efficient

What to test Expected inputs: – If used as intended are ‘normal inputs’ processed as expected Boundary inputs: – Inputs at the top and bottom limits of ‘normal inputs’ Invalid inputs: – Those which are unacceptable and may crash the program

Eg “Enter your age” ExampleInput TypeResult 12Valid (if Int data type)Program continues 12.5Valid (if Float data type)Program continues 1Boundary (minimum)Program continues 120Invalid (Too high)Error msg displayed. AbcInvalid (wrong data type)Error msg displayed NULL (no entry)Invalid (Cannot be “ “)Error msg displayed TwelveInvalid (wrong data type)Error msg displayed Each entry MUST be tested and the appropriate response confirmed. Errors MUST be trapped (identified) and addressed. Failure to do so will crash your program!!

Good Testing Does identify errors.. These are normal Usually need more time and more code than the program itself Must be structured and documented – What you tested – Where in the program – What was the outcome