QTP script test planning - guidelines?
Do any of you have experience in working with a QA group attempting to introduce QTP automation as a large function of the group initially? The company I work for has a scripting group in Pune, India and we are in Alpharetta, Georgia. What I need to know is.... lessons learned, process management, etc. that any of you have experience with. I appreciate anything you can throw at me that would help. Thanks!
Re: QTP script test planning - guidelines?
One lesson I've learned is that unless your upper management and their parallel peers do not completely commit to the migration, you'll make half hearted attempts here and there, spend loads of money and then the automation tool ends up being shelfware.
Management needs to accept that migrating takes time and usually that time is not allowed due to a need within the company. Now this may be true only if the software being considered for the migration is for the business and your "customers" are actually users within the company rather than paying customers outside the company. The investment that management makes in various projects to improve business invariably overlap. This I've seen as true because the migration timeframe and especially resources are rarely estimated correctly; usually far too short of an expectation was set with little understanding of the commitment involved. This understanding cannot be relied upon by those selling the software because their job is to sell the software and brief consulting services. An outside consultant with no connection with either company seems to help the situation but the bottom line is how far of a commitment a company is willing to make to be successful.