Testing

Testing Strategy
A general description of the type of testing you intend to use. For example, do you intend to complete system testing first, or module testing? Do you intend to test validation separately from functionality?

Test Plan
A list of tests, including test data that you intend to use. Each test should be numbered. You may wish to split your testing up into several section. Use the table below:

The 'Test area' should indicate which section of your implementation you wish to test. e.g. Validation Checks.
The 'Description of test' should explain why you are performing the test.
The 'Expected result' should explain what you expect the outcome of the test to be.
The 'Comment' should not be filled in until after the test has been completed, and should indicate whether the test was successful, i.e. did the expected result actually happen. A tick is sufficient to indicate that the test was successful, if something unexpected happened then you need to explain what happened and why.

Evidence of Testing
Screen shots showing what happened when you performed each test. You should paste the screen shots into a Word Processor and add an explanation saying what they show. You must also include the test number from your test plan.