A Test Plan must include,The identity of the component to be tested.The purpose of the testProgrammers' signatureTest data to be used.The expected outcome .

A test plan is a detailed document that outlines the test strategy, testing objectives, resources (manpower, software, hardware) required for testing, test schedule, Test Estimation and test deliverables. The test plan serves as a blueprint to conduct software testing activities as a defined process which is minutely monitored and controlled by the test manager.

Here are the steps to include in a Test Plan:

1. Test Plan Identifier: This includes the identity of the component to be tested. It could be a module, a function, a procedure, or any other software component.

2. Test Items: These are the software items that will be tested. It could be a function, a procedure, a module, a software package, etc.

3. Features to be tested: This includes the purpose of the test. It could be to verify the functionality, performance, reliability, security, etc. of the software component.

4. Approvals: This includes the programmers' signatures. It is a confirmation that the test plan has been reviewed and approved by the responsible individuals.

5. Test Data: This includes the test data to be used for testing. It could be input data, database data, files, etc.

6. Expected Results: This includes the expected outcome of the test. It could be the expected output, the expected performance, the expected behavior, etc.

7. Test Environment: This includes the hardware and software environment in which the tests will be executed.

8. Test Schedule: This includes the schedule of the testing activities.

9. Test Deliverables: These are the documents, tools and other components that need to be developed and maintained in support of the testing effort.

10. Staff and Training Needs: This includes the manpower required for testing and any training that needs to be provided to them.

11. Responsibilities: This includes the responsibilities of each team member.

12. Risks and Contingencies: This includes the potential risks and the contingency plan.

13. Approvals: This includes the signatures of the people who approve the plan.