Building & Testing the program P2 P4 P5 M3 D2

TESTING DOCUMENT
UNIT 14 EVENT DRIVEN PROGRAMMING




SUNDERLAND COLLEGE
Eliot Hunter

, Eliot Hunter (ID: 16002495) Assignment B Unit 14 Event Driven Programming




Testing Document


Strategy
To test my program to make sure it works, I will be recording each test inside a table which will be below. If any part of the program does not work as it is
supposed to, I will write the corrections that were necessarily made to correct the error. Inside of the table below, it will also contain the expected vs actual
result of the program and the data type. The requirements that the program needs are:

1. The car chosen, colour and how long for.
2. Add any extras (service) that the customer wants
3. Date of the invoice that was created
4. Customers contact details
5. Sign in page for the user
6. Start and end days of the hire and this includes how long for.
7. Show a 10% discount if hired for longer than 7 days
8. Grand total of the hire cost
9. Add any surcharge prices (service)
10. Help for the user
11. Validation so the program is robust
12. The company name and logo

This program was designed and developed for the car hire company called especially for you.



Test Data Test Expected Actual Correction
Number Type
1. Normal Program loads. The program should load without The program did load without None
any errors. errors.

1|Page