Purpose - Describe why the test plan was developed--what the objectives are. This may include documenting test requirements, defining testing strategies, identifying resources, estimating schedules and project deliverables.
Background - Explain any events that caused the test plan to be developed. This can include implementing improved processes, or the addition of new environments or functionality.
Technical Architecture - diagram the components that make up the system under test. Include data storage and transfer connections and describe the purpose each component serves including how it is updated. Document the layers such as presentation/interface, database, report writer, etc. A higher level diagram showing how the system under test fits into a larger automation picture also can be included if available.
Specifications - list all required hardware and software including vendors and versions.
Scope - briefly describe the resources that the plan requires, areas of responsibility, stages and potential risks.
Project Information - identify all the information that is available in relation to this project. User documentation, project plan, product specifications, training materials and executive overview materials are examples of project information.
Expand
Requirements
Requirements
Excerpt
This section of the test plan lists all requirements to be tested. Any requirement not listed is outside of the scope of the test plan.
Business Requirements - possible questions to ask:
What does the business do today?
How does it do this?
Who does it?
When and where does it happen?
Why is it needed?
Functional Requirements - possible questions to ask:
What are the functions?
What are the qualitative descriptions for the functions?
What is the context and relationship?
Who performs the activities?
Technical Requirements - possible questions to ask:
Are there any constraints that apply?
Are there any quality and performance related requirements?
