Once the approach is understood, a detailed test plan can be written. Usually, this test plan can be written in different styles. Test plans can completely differ from project to project in the same organization.

IEEE SOFTWARE TEST DOCUMENTATION Std 829-1998 - TEST PLAN

Purpose
To describe the scope, approach, resources, and schedule of the testing activities. To identify the items being tested, the features to be tested, the testing tasks to be performed, the personnel responsible for each task, and the risks associated with this plan.

OUTLINE
A test plan shall have the following structure:
· Test plan identifier. A unique identifier assign to the test plan.
· Introduction: Summarized the software items and features to be tested and the need for them to be included.
· Test items: Identify the test items, their transmittal media which impact their
· Features to be tested
· Features not to be tested
· Approach
· Item pass/fail criteria
· Suspension criteria and resumption requirements
· Test deliverables
· Testing tasks
· Environmental needs
· Responsibilities
· Staffing and training needs
· Schedule
· Risks and contingencies
· Approvals