Making a great Project 2Making a great Project 2

OCR 1994/2360OCR 1994/2360

TestingTesting

The point of testing is to make sure that it The point of testing is to make sure that it does what it set out to dodoes what it set out to do

Test to see that the user requirements Test to see that the user requirements have been methave been met

Test to see that validation rules workTest to see that validation rules work

Testing 1 – the testsTesting 1 – the tests

It is a good idea to plan your test strategy It is a good idea to plan your test strategy firstfirst

List your user requirements (from the List your user requirements (from the analysis) againanalysis) again

List your validation rules (from the data List your validation rules (from the data structure design) againstructure design) again

Print a list of all your data to show what is Print a list of all your data to show what is therethere

Testing 1 – the testsTesting 1 – the tests

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

Testing 2 – describe the resultsTesting 2 – describe the results

Say why you are using the data for the Say why you are using the data for the test.test.

For each test, forecast the exact results – For each test, forecast the exact results – eg say exactly which records should be eg say exactly which records should be returned by a query.returned by a query.

Testing 1 – the testsTesting 1 – the tests

Carry out each test. Carry out each test.

Provide a screenshot of the results.Provide a screenshot of the results.

If you use a table to lay out your test results, If you use a table to lay out your test results, make sure the format is suitable and that make sure the format is suitable and that screenshots are legible.screenshots are legible.

Testing 2 – describe the resultsTesting 2 – describe the results

Make a comment comparing the results to Make a comment comparing the results to your forecasts, and if it’s not what you your forecasts, and if it’s not what you expected, suggest ways you can fix it.expected, suggest ways you can fix it.

If you use a table to lay out your test results, If you use a table to lay out your test results, make sure the format is suitable and that make sure the format is suitable and that screenshots are legible.screenshots are legible.

Testing 1 – the testsTesting 1 – the tests

Think of ways to test your validation rules Think of ways to test your validation rules – but don’t go overboard on this.– but don’t go overboard on this.

Testing 2 – describe the resultsTesting 2 – describe the results

Say why you are using the data for each Say why you are using the data for each test.test.

For each test, forecast the exact resultsFor each test, forecast the exact results

Carry out the tests, providing a screenshot Carry out the tests, providing a screenshot and brief comments on each one.and brief comments on each one.

TestingTesting

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

Testing Complete…Testing Complete…

That’s it! You’ve done the Testing section.That’s it! You’ve done the Testing section.

Don’t forget about it – you will need to Don’t forget about it – you will need to refer back to it in your evaluation.refer back to it in your evaluation.