| || |
Requirement Collection in un-cooperative environment
The question goes like this:
You are asked to create a test strategy, test plan, completion dates and other documentation. Also to get a team together.
You are new to the application being tested. You don't know our internal technology. You don't know about how anything fits together. There is no documentation that was ever written. A QA department does not exist. Even worse no one wants to assist you. They are not co-operative because of QA being a threat and they say that they do not have time. The people with knowledge feel that it is not in their interest to guide you. What do you do to get the information?
I have heard this question on at least three interviews.
I usually say that I look for a manual tester doing drudge type work and show them how using the automation test tool can relieve them of their pain. Then I find a few more people like this and they see the advantage. I explain to them that automation testing pays better, can be learned easier than complex code such as Java and that I'd help them with the framework if they work with me. People like my style and the automation becomes something fun.
There must be some better answer. What is better or the correct answer?
I am sure a lot of consultants do feel the same way at the beginning of a new assignment. In fact, I've been in that situation a few times. The only way to impress anyone is with your work. Identify the subject matter experts and folks who would try to help and get as much information from them as possible. Then start creating your test plan and get it reviewed by the appropriate stakeholders and then you will get some good feedback (especially if they know you have the backing of your boss).