7 Tips on How to Write a Test Plan

TestFortExpert by TestFortExpert on 03/25/2013

7 Tips on How to Write a Test Plan

If you do not like a standard template of a test plan or you decided to come up with your own document format more suitable for you, you should know that a good test plan must at least describe the following:

1. What should be tested?

2. What will you test?

3. How are you going to test?

4. When are you going to test?

5. Criteria for beginning of testing:

6. Criteria for ending of testing:

Further, to make your document less serious, you should add the following issues to it:

Most often, in practice, one faces with the following types of test plans:

  1. Master Plan or Master Test Plan
  2. Test Plan
  3. Product Acceptance Plan (a document describing a set of actions related to acceptance testing (strategy, date, officials, etc.)

A Master Test Plan is more static in comparison with a simple Test Plan because it contains High Level Information which is not subject to rapid changes in the testing process. A Test Plan that contains more specific information on strategies, types of testing, scheduling is a “living” document that is constantly changing.

In everyday life the project can have one Master Test Plan and several detailed test.

7. Review and Approval

To increase the value of your test plan conduct its periodic peer review by members of the project team. Below you will find a possible list of participants of the project team:

Their comments and suggestions will help you to make a test plan more complete and qualitative.

Using the above tips you will most probably write a good test plan and won’t have to invent everything by yourself.

We use cookies to ensure your best experience. By continuing to browse this site, you accept the use of cookies and "third-party" cookies. For more information or to refuse consent to some cookies, please see our Privacy Policy and Cookie Policy