|
Test Plan should be updated anytime according to your other works, such as
requirements analysis, development plan and so on. If this is a project or
little project, maybe the test plan does not reflect anything. If this is a
product, and would be tested version by version, the test plan should be
updated version by version.
Perhaps you should know that test plan has a patten including a lot of
items. You can write some of them but not all. With the improvement of your
prodcut, you could write other items and make the test plan comprehensive.
Another usage of test plan is to make the whole test work coordinative. If
some things take place, you would add them into your test plan. Maybe one day
your test plan would include a lot of contents, it could be as a reference to
you, to other people, to your leader.
Don't ignore Test Plan. Maybe you could not get its importance now. But
it's really improtant. |
|