|
How do you write a software test plan?
|
|
|
|
Q: How do you write a software test plan?
A:
First we work with management early on to understand how software requirements
might change, so that alternate test plans can be worked out in advance.
It is helpful if the application's initial design allows for some adaptability,
so that later changes do not require redoing the application from scratch.
Then we focus less on detailed software test plans and test cases, and more on
ad-hoc testing with an understanding of the added risk this entails.
We design some flexibility into software test cases; this is not easily done;
the best bet is to minimize the detail in the test cases, or set up only
higher-level generic-type test plans.
We write software test plans, by describing the scope, approach, resources,
and schedule of intended testing activities. In the test plans we define the
scope, approach, resources, and schedule of the intended testing activities.
We create a software test plan, and preparing it helps us to think through
the efforts needed to validate the acceptability of a software product.
We create a test plan by helping people outside the test group to understand
the why and how of product validation.
We create a test plan by describing and documenting the objectives, scope,
approach and focus of the software testing effort.
We create a test plan by including test cases, conditions, the test
environment, a list of related tasks, pass/fail criteria, and risk assessment.
We create a test plan because one of the outputs for creating a test strategy
is an approved and signed off test plan document. We create a test plan because
the software testing methodology a three step process, and one of the steps is
the creation of a test plan. We create a test plan because we want an
opportunity to review the test plan with the project team.
We create a test plan document because test plans should be documented,
so that they are repeatable. Documentation plays a critical role in QA.
QA practices should be documented, so that they are repeatable. Documentation,
including test plans, should all be documented. Ideally, there should be a
system for easily finding and obtaining of documents and determining what
document will have a particular piece of information. Use documentation change
management, if possible.
Link to this article!
Link to this article from a forum!
|
______________________________________________________
|