while implementating any test automation frame work what are the difficulties we face with QTP irrespective of any tool.u said every tool has it's own short comings , ineed these short comings regarding QTP
Most of the shortcomings come from the automator or misunderstandings of the people who just had to have this tool and didn't do a lot of research. Why not focus on the positives? What is the purpose of your need? What is the context?
Please come up with valuable answers, who said that limitation of particular tool is inability of the people working on that tool, if i list out the limitations of QTP then will u log out from QAforum ?
Hmm. Limitations. Well my bias for a programming language is 'C,' not VB. So every time I go to program I have to translate on the fly (think in C, write in VB derivative). So, I call this a limitation. You can decide is this is a personal limitation or a tool based one.
On the tool side, let's see. QTP doesn't support the following apps/dev environments.
<ul type="square">[*]PowerBuilder[*]Baan[*]Centura[*]Delphi[*]Forte[*]Siebel 5&6[*]SmallTalk[*]Stingray[*]explicit Clarion objects[/list]
It only runs on Windows. If I have to test something that runs in X-Windows I have to move to another Mercury tool which has a different language. I would call this a limitation.
It doesn't run on my copy of Windows 3.1 that I keep around for compatibility testing. I would call this a limitation.
The box is not quite heavy enough to use a doorstop to keep the hydraulic arm from closing my office door. I would call this a limitation.