The Blog

I Love It When A 'Test Plan Template' Comes Together!

Posted by Phil Edwards on 24/01/2017

Firstly, a Test Plan, in simple terms, is a testing project plan for all the testing works that need to be achieved during any of the test phases; the test plan will not address test design, nor detail the low-level details of say a Test Case or Test Script. It is however vital that you have a good test plan template so that you always start right and have the required sections in the template to allow you to: 

  1. Be thorough
  2. Use the latest version of the document thus giving you the best opportunity to cover of all the details required for that Testing Phase.

I love it when a test plan template comes together.jpg
IEEE 829 mandates that the following items must be included in your Test Plan:

  • Test plan identifier
  • Test deliverables
  • Introduction
  • Test tasks
  • Test items
  • Environmental needs
  • Features to be tested
  • Responsibilities
  • Features not to be tested
  • Staffing and training needs
  • Approach Schedule
  • Item pass/fail criteria
  • Risks and contingencies
  • Suspension and resumption criteria Approvals
For those of you working in an Agile fashion it’s clear that you’re unlikely to have the time to fill out all these details for every sprint. That is okay, you can have a master test plan that cover these off and have alight test plan specific for your Sprint that can reference back to the master test plan.

Secondly, the Test Plan is a great tool for communicating what you are going to be doing, when it’s being done and by whom. Without the test plan the larger project team may not know what you are doing nor the benefits of why you are doing it; we all know the benefits of having buy-in from stakeholders, so make sure that once the Test plan is created that it is distributed accordingly.

And lastly, with best intentions, all projects can change direction or shape at any point; budgetary and time constraints may alter you test approach and how much testing you need to do. Therefore, plans need to change in accordance with that, be prepared for the test plan to be a working document and update it when necessary but don’t lose the fundamentals of what the desired outcome needs to be. Always remember to get sign-off when making changes. Starting with the right test plan template will give you the best opportunity to have a complete and thorough document.

Download out white paper on the benefits of adopting Agile

Topics: Software Testing, test plan template

nFocus Blog

Welcome to the nFocus software testing blog. As thought leaders and technical innovators, we created this blog to distil our thoughts, ideas and musings on improving software quality.

Fill out the form below to receive future communications from nFocus including our latest:

  • Blog articles
  • White Papers
  • and plenty more!

Subscribe to Email Updates