Testing : Evidence

You may include evidence of both formal and informal testing in a project report. It is vital that evidence of formal testing using your test plan is included.

You must explain by annotating (writing on) any printouts you produce exactly what the printout shows and how it relates to your test plan.

Note that :

1. You should carry out every test that you listed in the test plan.
2. Some tests may not be passed immediately. If a test is failed then the problem that caused the failure should be located. The problem should be put right and the test should be carried out again.
3. It does not matter if some of the tests are failed and not corrected. What is important is that you identify the failures, explain them in the testing, and note them as limitations of the system in your evaluation.

If you carry out a test (whether or not it is included in your test plan) and decide to modify your system then always include evidence of the test in your documentation.

For each test you carry out you should include this information in the testing section of a project :

• The actual results, which are the printouts that you obtain when the test is performed.
• Enough annotation to explain whether or not the actual results match the expected results set out in the test plan.
• A conclusion stating whether or not the test has been passed.

It is a good idea to try and present an overall summary of the results of all of your tests in a table.

GCSE ICT Companion 04 - (C) P Meakin 2004