Testing

Terms 1 Test Data: The data you will enter to test your system Test Plan: A plan of the tests you are going to complete to ensure your system works Test strategy: Strategy for testing, i.e. What sort of tests will be done first Corrective Action: What action you need to take if you find that your system is not working correctly. End User Testing: Tests carried out by the person who wants the system to ensure it matches their requirements

Types of test Validation: What you enter is sensible and can be accepted Navigation: Tests that you can navigate around a page or site as required System Tests: Check the system works. E.g. Formulas add up correctly Protection tests: Ensure that you can only enter data where required Security test: Test passwords etc.

Terms 2 Normal Data: Data that will be accepted. E.g. A number in a number field Abnormal: Data that will not be accepted, e.g. A letter (e.g. A) in a number field Extreme: The first and last thing that will be accepted. E.g. In a range of the extreme data would be “1” and “100”

Example If you were entering exam percentages you might have the following test data: Normal: 55 Abnormal 110 Extreme

Test Plan: Show what you want to test Test NumberWhat is being tested and description Test DataExpected OutcomeActual ResultsCorrective action e.g. 1Hyperlink between slide 1 and 2. Click on Link on slide 1. N/AGo to slide 2 e.g.Can enter number in number field 5Be accepted Draw out a table like the one below to plan what tests you need to do on your system: