Posts: 2
Threads: 1
Joined: Sep 2009
Reputation:
0
09-10-2009, 11:29 AM
Hi,
We are trying to automate a web application which is developed on TIBCO General Interface.All the objects in the application are getting recognized as WebElement.Please let us know if any add-in is required for recognizing the objects.Here we are using QTP9.5 version.
Thanks In Advance,
Monika
Posts: 1,199
Threads: 5
Joined: Nov 2008
Reputation:
0
09-10-2009, 11:50 AM
QTP should work for a web application. Can you check that you have opened your application after opening QTP?
also check the web Addin is properly loaded.
Posts: 2
Threads: 1
Joined: Sep 2009
Reputation:
0
09-10-2009, 12:30 PM
QTP is working,but it is capturing all the objects as WebElements.Also we have opened our application after opening QTP.
Posts: 159
Threads: 0
Joined: Mar 2009
Reputation:
0
09-10-2009, 01:23 PM
Hi,
Can you try executing 'SettingNewBrowserControlApplication.exe' file.
You will find it at the below mentioned location.
C:\Program Files\Mercury Interactive\QuickTest Professional\bin\SettingNewBrowserControlApplication.exe
Posts: 1,199
Threads: 5
Joined: Nov 2008
Reputation:
0
09-10-2009, 01:34 PM
(This post was last modified: 09-10-2009, 01:44 PM by Saket.)
Hi Tarik,
the utility you have mentioned is for adding browser functionality to non-Web application. It registers to identify the browser control used in a particular application. This is not to register web objects, so it will not work in this case.
Monika - can you please take a spy of your control and attach the snapshots here?
Posts: 159
Threads: 0
Joined: Mar 2009
Reputation:
0
09-10-2009, 01:48 PM
Hi,
Oh. Ok. I guess in that case a screenshot will be helpful.
Posts: 1,199
Threads: 5
Joined: Nov 2008
Reputation:
0
09-10-2009, 03:02 PM
I just tried to spy on a page developed with Tibco, QTP identifies some objects like webCheckbox, webedits, images..
but it identifies as webelement for all custom controls (i guess), saying class as jsx30...
I dont think there is any add-in available for these controls now. So you will have to work with the current identified only, firing the proper event required.
also you can try Web extensibility to make QTP identify these controls.
You may raise a case at HP for this.
