Test strategy

What is it?

Before you start implementing the system you must decide on how to test it. Using your design you need to consider what tests must be run to ensure that the program can be deemed working. It will normally take the form of a table.

Testing layout

All of your tests must be in the following table.  You will have one for every form in your system.

Test num

Description of test

Test data

Expected outcome

Actual outcome


Ensure that login works for a standard user

Username – Bob
Password - doody

Will take the user to main form (form 1)


Each form must have its own table like this. To make life easier for you it is best to lay this out in sections. Each form will have its own section and you will include -

The input form is not needed but it should make things a bit easier.

What should be tested

You need to test the following –

You will end up with a lot of tests! This is a good thing! There are a lot of marks over the project for testing so although there are only 5 marks here, later on there are many more marks to be had!

Mark boundaries


5 marks

A detailed test strategy and plan covering all aspects of the system with data to test under normal, extreme and abnormal circumstances.

3–4 marks

A detailed test strategy and a plan covering several aspects of the system but with inadequate data to effectively test the system, eg data covers only normal circumstances or covers only a limited part of the design specification.

1–2 marks

A vague discussion of how the system might be tested.






High mark boundary

Middle mark boundary

Low mark boundary

Top tips