How to Work out a Proper Test Plan?

May 29 10:00 2014 by Nataliia Vasylyna Print This Article

No mobile testing, desktop testing or web site testing can be performed without a plan. It is commonly believed that developing of a test plan is a long, labour-intensive process. It is so.

But due to time limitations it is unprofitable to spend much time on a test plan. This mostly relates to mobile application testing, as mobile projects are often very limited in time.

Besides, requirements to a test plan execution became less severe. Most of software testing experts agree that the most important about a test plan is its efficiency, not its formatting or volume.

Software testers have elaborated easy ways of creating effective plans for manual and automated testing.

For Example, James Bach Claims That a Good Test Plan May be a Combination Of:

• the project analysis;
• the test strategy;
• the risk analysis;
• the logistics.

Any software testing company notices that less formal are mostly plans for mobile projects.

Nowadays a Test Plan Can Be:

• a formal document;
• a to-do list in an application or on paper;
• a few lines on a whiteboard or a notepad.

One of significant characteristics of a good test plan is its flexibility and adjustability. It must be easy to change the plan if something in the project is changed.

Learn more from QATestLab

Testing
Services

Solutions
by Industry

Related Posts:

• Main Parts of Successful Test Plan
• On What Documents Should a Test Plan be Based?
• What Should Be Included in a Test Plan?