Test Plan 
All test plans are slightly different in their scope and form. This section is just a recommendation of some contents to consider when putting together an effective plan that can guide a testing effort. 


Project Name: 
<Project name - can be product name, release, or other identifying factor> 


Component Name: 
<Name of the component> 


Feature Name: 
<General name of the feature> 


Development Resources: 
<Developers responsible for this piece of the project> 


Test Resources: 
<Testers responsible for this piece of the project> 


Other Resources: 
<Other resources involved: management, usability experts, designers, and so on> 


Timeline: 
<Dates the development is expected to start, coding is expected to finish, testing is expected to begin and end> 


Requirements: 
<Several paragraphs or specifications about this piece, references to more detail. Discussions of architecture, platforms, clients, and so on can be drawn out here.> 


Limitations: 
<Specific limitations or what this feature is acknowledged as not accomplishing> 


Risks: 
<Areas or potentially problematic aspects of this piece of the project> 


Plan: 
<High-level discussion of what needs to be considered for this piece of the project. Should be fairly detailed, though> 


Specific Test Cases: 
<There may be some specific test cases outside the obvious that need to be called out, either due to their high risk or their importance.> 


Other References: 
<Are there previous or planned future iterations on this feature? Are there other documentations or areas that overlap with this?>