[ QUOTE ]
The major grouse of my customer is that QTP tests takes long to run. I have been trying to tweak code.
[/ QUOTE ]
I doubt that "speeding up" vbScript functions is going to improve overall performance of QTP tests. Unless you have a very unusual app, or are using QTP for non-UI testing, virtually all of the time is spent navigating the app, and or waiting for windows and controls to be ready.
I tried to make the customer see that the QTP is fast as the app. The customer is not ready to buy my idea that the QTP is essentially to offset a testers effort. I told the customer that automation should relieve the testers from executing the mundane test cases and help them find more time to test creatively.
My coordinator says that the guys there could be impressed only if the tool expedite the test cycle.
It would require me to write a long mail about their myths. Citrix metaframe also contributes to my pains [img]/images/graemlins/smile.gif[/img].
Well, you might as well write the email because there is nothing you can do to beat the UI interaction between QTP and the AUT. And virtually any attempts you try to "speed" that interaction up will probably make the test unreliable.
If this is not self evident to your customers (Dilbert's boss once said: "what I don't understand must be easy..."), especially with a small overview on the issue, you need new customers, as these folks are real bozos.
I feel your pain (or I should say I have at so many different places over so many years).