Does anyone have a list of things that can not be done/programmed when using QTP for GUI automation.
I like to know this since we are at the begining of our automation and I like to see what other tools we might need.
Thanks in advance.
[/ QUOTE ]
QTP is limited by the person who uses it!
I've used it for a while and don't pertain to knowing everything. When I need to achieve something, I look up help/sqaforum/t'internet and see if someone else has done it, or try myself and see if I can do it. If not, then it's a limitation!
I know it was a loaded question. [img]/images/graemlins/smile.gif[/img]
About your dream cars, I guess now we can both call rong. [img]/images/graemlins/smile.gif[/img]
Thanks rong, I am just trying to build up a case for choosing a right tool for automation. I have used Silk, QTP, Perl and now I can automate or drive the GUI using C# which I find interesting.
[/ QUOTE ]
Ok I have had my fun now...
You can do almost (note i did say almost) everything a user can do with automation. Sometimes it takes a bit of creative coding and working around the limitations in QTP. One big hint is never use QTP checkpoints there is enough flexability in the available commands to write custom checkpoints.