Test Plan

1. Usually prepared by the Test Lead or Test Manager

2. Derived from the Product Description, Software Requirement Specification SRS, or Use Case Documents.
 
3. The focus of the document is to describe what to test, how to test, when to test and who will do what test. It is not uncommon to have one Master Test Plan which is a common document for the test phases and each test phase have their own Test Plan documents.
 
4. Main Components are:
    - Test Plan id
    - Introduction
    - Test items
    - Features to be tested
    - Features not to be tested
    - Test techniques
    - Testing tasks
    - Suspension criteria
    - Features pass or fail criteria
    - Test environment (Entry criteria, Exit criteria)
    - Test deliverables
    - Staff and training needs
    - Responsibilities
    - Schedule