Suggested Test Plan Components

Item	Description
1	System/product to be tested, including version and release (as applicable)
2	Test plan version and date
3	Test phase
4	Test objectives and scope, including any interfaces that will be tested
5	Description of business and system requirements, detailed design, and program specifications that will be used to test against (may be a reference to other documents)
6	Requirements Traceability Matrix (RTM) to tie test cases/scripts and test events to the requirements (may be a reference to other documents)
7	Test cases and test tools to be used
8	List of testing staff and contact information
9	Test environments to be used (hardware, software, network, test regions)
10	Testing schedule (on-lines, batch processes, data refresh, etc.)
11	Description of test deliverables and due dates
12	Physical location(s) of testing activities and logistics for carrying out test events
13	Training plan for training test team
14	Configuration management process (version control, change management, risk analysis and mitigation related to all system areas supporting the testing effort). This may be a reference to other plans, such as configuration management, change management, risk management, etc.
15	Plan for technical support during the testing phase
16	Communication and documentation plans for recording, storing, sharing and tracking test events, test results, screen prints, problem reports, status reports and general communications during the testing phase.
17	Problem resolution plan for logging, reporting, prioritizing, and tracking defects from the point of discovery to fix and retest
18	Change management plan to manage scope issues and change requests that surface during testing
19	Methodology for tracking and reporting testing progress
20	Acceptance criteria for authorizing code moves from one test phase to another, including readiness for pilot or full implementation
21	Production verification plan to execute final Quality Assurance check before going live (if applicable for the test phase)
22	Back-out plan if code fails in test regions or after deployment to production