Test Plan


A TEST PLAN is a document describing software testing scope and activities. It is the basis for formally testing any software/product in a project.



Test Plan Template


Test Plan Identifier:

  • Every test plan must have a unique Identifier that may contain information about the version, type of the test plan, etc. for example: ‘Master Test plan for Workshop Module TP_1.0’ :


Introduction:

  • Provide an overview of the test plan.
  • Specify the goals/objectives.
  • Specify any constraints.


References:

  • List the related documents, with links to them if available, including the following:
  • Project Plan
  • Configuration Management Plan


Test Items:

  • List the test items (software/products) and their versions.


Features to be Tested:

  • List the features of the software/product to be tested.
  • Provide references to the Requirements and/or Design specifications of the features to be tested


Features Not to Be Tested:

  • List the features of the software/product which will not be tested.
  • Specify the reasons these features won’t be tested.


Approach:

  • Mention the overall approach to testing.
  • Specify the testing levels [if it’s a Master Test Plan], the testing types, and the testing methods [Manual/Automated; White Box/Black Box/Gray Box]


Item Pass/Fail Criteria:

  • Specify the criteria that will be used to determine whether each test item (software/product) has passed or failed testing.


Suspension Criteria and Resumption Requirements:

  • Specify criteria to be used to suspend the testing activity.
  • Specify testing activities which must be redone when testing is resumed.


Test Deliverables:

  • List test deliverables, and links to them if available, including the following:
  • Test Plan (this document itself)
  • Test Cases
  • Test Scripts
  • Defect/Enhancement Logs
  • Test Reports


Test Environment:

  • Specify the properties of test environment: hardware, software, network etc.
  • List any testing or related tools․


Estimate:

  • Provide a summary of test estimates (cost or effort) and/or provide a link to the detailed estimation.


Schedule:

  • Provide a summary of the schedule, specifying key test milestones, and/or provide a link to the detailed schedule.


Staffing and Training Needs:

  • Specify staffing needs by role and required skills.
  • Identify training that is necessary to provide those skills, if not already acquired.


Responsibilities:

  • List the responsibilities of each team/role/individual.


Risks:

  • List the risks that have been identified.
  • Specify the mitigation plan and the contingency plan for each risk.


Assumptions and Dependencies:

  • List the assumptions that have been made during the preparation of this plan.
  • List the dependencies.


Approvals:

  • Specify the names and roles of all persons who must approve the plan.
  • Provide space for signatures and dates. (If the document is to be printed.





Useful Links։
Test plan article/eng
Test plan video tutorial/eng
Test plan video tutorial/rus
Test plan, Test case video tutorial/arm

Content