Who should write the test plan?
- by Cheng Kiang
Hi,
I am in the in-house development team of my company, and we develop our company's web sites according to the requirements of the marketing team. Before releasing the site to them for acceptance testing, we were requested to give them a test plan to follow.
However, the development team feels that since the requirements came from the requestors, they would have the best knowledge of what to test, what to lookout for, how things should behave etc and a test plan is thus not required. We are always in an argument over this, and developers find it a waste of time to write down things like:-
Click on button A.
Key in XYZ in the form field and click button B.
You should see behaviour C.
which we have to repeat for each requirement/feature requested. This is basically rephrasing what's already in the requirements document.
We are moving towards using an Agile approach for managing our projects and this is also requested at the end of each iteration.
Unit and integration testing aside, who should be the one to come up with the end user acceptance test plan? Should it be the reqestors or the developers?
Many thanks in advance.
Regards
CK
