| || |
Why we need to upddate Test plan always
The top management was feeling that when there are any changes in the technology being used, development schedules etc, it is a waste of time to update the Test Plan also from time to time. Instead, they are emphasizing that you should put your time into testing than working on the test plan.Your Project Manager asked for your opinion. You have argued that Test Plan is very important and you need to update your test plan from time to time.It is not at all a waste of time and testing activities would be more
effective when you have your plan clear.Can any one explain with some metrics, how you
would support your argument to have the test plan in place all the time.
Re: Why we need to upddate Test plan always
New technology means other risks. Some existing development that were very complex with the old technology might be less complex now compared to others. So your test strategy will change, so your testing will change...
Development schedule changes. Important features are suddenly later delivered to the test team. The risk for the test effort is changing as there might not be enough time before the scheduled delivery date to test those important features. Risky, risky... so again the strategy might change, so your testing will change...
Some change somewhere will change the project risks, so testing should change. Where is the approach documented: the test plan.