Well here's my 2 penny worth re those documents plus the good old Test Policy document.....
A Test Policy document is a very high level company wide document and is written at the executive level. It'll consider the overall approach, culture and standards of the organisation, and will outline the corporate view of testing practices and is often written by the IT department.
A Test Strategy document describes how the testing should be done - how to implememnt the Test Policy. It will show what testing needs to achieve in order to reduce or even remove generic risks. It's a reusable set of testing guidelines and is usually not project specific.
The main difference between these two documents is their level of detail. The Policy is the 'what' and the Strategy is the 'how'.
A Test Plan is project specific and would include:
1. A Test Plan identifier
2. An introduction
3. Test items
4. Features to be tested
5. Features not to be tested
7. Item pass/fail criteria
8. Suspension criteria and resumption criteria
9. Test deliverables
13.Staffing and training needs
15.Risks and contingencies
How to test your product what type of methodologies your planning to test your product(like functional,performance, system testing etc....).
If you can plan to test your product in functional testing then you can choose the following testing depend upon your requirement
1.functionality testing(GUI Actual/Excepted values)
2.Input domian testing.(passing input values for testing)
5.Object Property checking
10.Inter system testing
Based on above testing your can prepare strategy document in the same document you can say why we are choosing above testing what is the advantages of particular test in our product like that you can implement test strategy document.
Once you decide test strategy then you can plan what are the modules you want to test,schedules, risks etc..... this need prepared one more document for test plan