menu

7 Tips on How to Write a Test Plan

2 m read

0%

Automated Testing, Functional Testing, Tips & Tricks

Spread the love

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?

  • Description of testing object (system, application, hardware)

2. What will you test?

  • A list of features and description of the system under test and its components taken separately

3. How are you going to test?

4. When are you going to test?

  • Sequence of activities: Test Preparation, Testing, Test Result Analysis in the context of the planned phases of the development

5. Criteria for beginning of testing:

  • Test platform readiness (testbed)
  • Completeness of the required functionality development
  • Availability of all necessary documentation

6. Criteria for ending of testing:

  • Test results meet the criteria of the product quality:- requirements for the number of open bugs are met- certain period without changing of the source code passed- certain period without opening new bugs passed

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

  • Environment of the system under test (a description of software and hardware)
  • Required test equipment and software (the test stand and its configuration, software for automated testing, etc.)
  • Possible risks and risk management

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:

  • Lead Tester
  • Test Manager (Quality Manager)
  • Head of Development
  • Project Manager

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.

No comments

Your comment will be shown after moderation.
Your email address will not be published.

This field is required.

Sing in to write comment

SHARE YOUR PROJECT IDEAS
Realizing the importance of providing service on agreed terms, we consider all possible risks and provide efficient solutions for all possible risks and provide efficient solutions.


Yes












Your information was successfully submitted.

  We are glad to have you with us! You'll receive an email from us shortly. Meanwhile, you can check our super-informative blog to go through the latest updates in the world of software development.Got it