You need the following mark scheme headings in b(iii) of your project:

• Test strategy.
• Test plan.

Remember - approach this section as if you were providing information for someone else to design the system.

Test strategy.
You should discuss your approach to testing. You may also want to describe why you will draw up your test strategy and plan before you begin coding. In your discussion here, you should mention the need to test as you develop code (white box testing) and give some examples of the kinds of things you would test and the kinds of tests you would carry out. You should also discuss the need to test the final solution against the Requirements Specification (black box testing) and how you would go about doing this. The third part of this sub-section is to describe user testing, why you would carry it out and how you will go about this. You fourth area to consider is the need for acceptance testing; what it is and how you will carry it out.

The test strategy is all about describing and justifying an overview to testing, a broad approach.

Test plan.
You should draw up 4 separate plans, each done as a table.

Test Plan 1 will be Testing during development (white box testing). in a table, you should state what you will test, what data you will use, why you have chosen that data, what you expect the outcome to be and the results. There also needs to be a column for the page numbers of the evidence that the test has been carried out. You could plan to test some of your algorithms. You might want to fully test a couple of validation rules. Your teacher will advise you on the appropriate number of tests for your particular project.

Test Plan 2 will be Testing post development (black box testing). In a table, you should state each of your Requirement Specifications, the data you will use to test each one, why you choose that data, what you expect the outcome to be. There also needs to be a column for the page numbers of the evidence that the test has been carried out.

Test Plan 3 will be User testing. In a table, write down what you will ask your user to do, why you are asking him to do that test (what are you testing), what data you will use, why that data and what you expect the outcome to be. You are doing user testing to check that the user can use the system competently and get help when they get stuck. There also needs to be a column for the page numbers of the evidence that the test has been carried out.

Test Plan 4 will be Acceptance testing. At the end of the project, you need to agree with the user that it does what you both agreed it would in the Requirements Specification. The user will therefore need to carry out out the things identified in the Requirements Specification. If they are happy it all works, then they can sign it off. There also needs to be a column for the page numbers of the evidence that the test has been carried out.

You could also plan to do Acceptance testing as part of your User testing and have 3 tables instead of four. Your teacher can advise you on the best way forward for your particular project.

CHECK:

ARE YOU USING YOUR TEMPLATE(S)?

ARE YOU USING REPORT WRITING STYLE?

HAVE YOU BEEN UPDATING YOUR DIARY?