Why are we writing a test plan?

Why should we write a test plan?

Take technology
2007-9-23

Original: Why do we write a test plan–ainars Galvans

We should not write the test plan so long as to be daunting, nor to write so short that it is meaningless and neglected.

A template is a good thing, but a template shifts the author's attention away from the goal of the plan-the target will vary depending on the project.

Planning can be a very complex, imprecise and time-consuming process, but the test plan written out will not reflect these.

Planning is about thinking about how to do something.

Lack of planning, empowerment, reliance on their skills, commitment, teamwork, not just silver bullets, but a lot of drawbacks. For example, it is more difficult to measure and evaluate the performance of each individual without the retention of historical records.

Test plans are often presented to management as important documents about quality. The 4 elements of a project are covered by different documents: time-covered by the project plan, cost-covered by the contract, scope-covered by the requirement document, quality-covered by the QA program or test plan.

The internal and external effects of the test plan. External is to give the customer a confidence, about the test process, skills, resources, tools and other information.

There are 3 internal functions:
As a result of the test plan, let the relevant people and developers to review.
Store the details of the plan execution and let the tester perform peer review.
Store planned schedules, test environments, and more.