What is it?

This is testing you do once the implementation has been completed. It is broken into two parts

Alpha testing

You will have already done some testing already during development. This alpha test is done right at the end of the implementation. To do this you must –

When you take a screen shot label it with the test number that it relates to.

End user testing

Your end user should test the system using your test strategy and just using the system for real. They then should write a short statement saying

It is critical that they are not too nice here! We expect bugs and problems so your user should clearly state any issues they have with it.  They then should sign the statement.

Mark boundaries

11–14 marks

The testing covers as many different paths through the system as is feasible, including valid, invalid and extreme cases. The testing covers all aspects of the design specification and the test plan from the design section. There is clear evidence of end-user testing.

8–10 marks

There is evidence of testing covering most aspects of the design specification but with omissions, eg test data does not include erroneous data for all tests or there is limited evidence of end-user testing.

5–7 marks

There is limited evidence of testing based on a badly developed test plan with clear omissions. There is no description of the relationship between the test plan and the testing in evidence.

1–4 marks

A collection of hardcopy test run outputs with no clear link to the test plan and covering few aspects of the system. No evidence of end-user testing.

High mark boundary

Note – if you did a good test strategy then this will be easy marks!

Middle mark boundary

Low mark boundary

Top tips