1. Making a great Project 2 OCR 1994/2360

2. Testing The point of testing is to make sure that it does what it set out to do Test to see that the user requirements have been met Test to see that validation rules work

3. Testing 1 – the tests It is a good idea to plan your test strategy first List your user requirements (from the analysis) again List your validation rules (from the data structure design) again Print a list of all your data to show what is there

4. Testing 1 – the tests Think of ways to test that you have met the user requirements (eg by running a query or report).

5. Testing 2 – describe the results Say why you are using the data for the test. For each test, forecast the exact results – eg say exactly which records should be returned by a query.

6. Testing 1 – the tests Carry out each test. Provide a screenshot of the results. If you use a table to lay out your test results, make sure the format is suitable and that screenshots are legible.

7. Testing 2 – describe the results Make a comment comparing the results to your forecasts, and if it’s not what you expected, suggest ways you can fix it. If you use a table to lay out your test results, make sure the format is suitable and that screenshots are legible.

8. Testing 1 – the tests Think of ways to test your validation rules – but don’t go overboard on this.

9. Testing 2 – describe the results Say why you are using the data for each test. For each test, forecast the exact results Carry out the tests, providing a screenshot and brief comments on each one.

10. Testing Don’t do more tests than absolutely necessary to test the user requirements – you are likely to get more marks for 2 tests done well than 20 tests done badly!

11. Testing Complete… That’s it! You’ve done the Testing section. Don’t forget about it – you will need to refer back to it in your evaluation.