On What Documents Should a Test Plan be Based?

On What Documents Should a Test Plan be Based?
June 05 10:00 2014 Print This Article

Every novice tester knows that a test plan is an important document. It contains significant information about the testing process and instructions on how to execute mobile testing, desktop testing or web site testing.

However in reality it often turns that on one reads a test plan, as it is a big useless document copied from the previous software release or created by filling a standard template. It takes much time and efforts to maintain such a document. So, a lot of time and efforts spent on test plan elaboration appear to be wasted.

Originally a test plan is meant to be actively used and consulted during manual and automated testing. That is why it should be useful, convenient, and contain current, updated information.

Some software testing experts suggest creating a test plan basing on several short distinct documents.

The Documents on Which a Test Plan May be Based Are:

  • analysis of the project;
  • the testing strategy;
  • the document containing information about the logistics issues;
  • the risk assessments.

It may be necessary to change the test plan in course of mobile application testing, desktop testing or web site testing. Any software testing company would agree that using the mention documents, one can relatively fast and easily elaborate a new, completely different test plan from the ground up.

Related Posts:

About Article Author

view more articles
Nataliia Vasylyna
Nataliia Vasylyna

View More Articles


write a comment

No Comments Yet!

You can be the one to start a conversation.

Add a Comment

Your data will be safe! Your e-mail address will not be published. Also other data will not be shared with third person.
All fields are required.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.