I would like to know your points of view on the following:
For a (not to complicated) new piece of functionality, which will be added to our existing application, I have written a testplan according to ISTQB standards. This has been reviewed by a collegue before submittal and was considered a good plan.
Now I have to get this plan approved and the person that has to do so feels he does not understand what we are going to test from the information in the plan. He reads the techniques and risks, strategy and all... but finds it not very important. He feels that the determination of "scope" should include a full descrition of the functionality we are going to build/test.
My position is that this information is part of the testbase and has no place in the testplan.
I have tried to negociate (but admit I am not very good at it) and I have offered him that I will write a max of 20 lines regarding the subject in the plan. But to no avail. He wants a FULL description. The reason for this is that he is unable to read the designdocument (120 pages of tech info.)
How do you guys feel about this? Should this info be part of my plan?
It sounds like he needs a document stating what the requirement is and that you don't have one. If you did you'd just point him to that document.
Maybe if he needs that document written he should task someone with creating it. It needs to be a seperate document and needs to be written correctly (correct, complete, consistent, feasable, testable, traceable, unambiguous) which is why people are trained to write documents this way.
I don't think that a test plan is the place to put this information, that's not it's purpose.
You might say the scope (or features to be tested) includes the login function, but you wouldn't say you're going to test that a valid username and password is accepted; and a valid user and invalid password is rejected; and you're going to test that a blank username and password is rejected; etc...
Putting all this in would be duplicating the test cases you'll be writing.
Good luck, Steve
Everywhere's within walking distance if you have enough time.
>>and I have offered him that I will write a max of 20 lines regarding the subject in the plan. But to no avail. He wants a FULL description.
I think this is a very valid proposal. We usually include a 'high-level' functional scope summary in the test plan and it's the actual test cases that will show the details.
For me it really depends on the quality/quantity of information available at the time the test plan is written. But to include a detailed functionality list in the test plan would be from my perspective kind of overkill.
>> Now I have to get this plan approved and the person that has to do so feels he does not understand
It would be interesting to know who this person is. The project manager maybe? I'm sometimes not too inclined to do what people tell me out of the QA/Testing area - unless in makes sense to me of course - and try to explain my reasons why I'm doing it this way.