HI ,
I am doing a automation POC on .NET application which has used Infragistics controls using UFT 11.50. I am using Infragistics evaluation ADD-in
.Net application which i am working has 'Infragistics.Win.UltraWinToolbars.UltraToolbarsDockArea' control which has many buttons. When i click on a toolbar button it will display a floating screen.
My Issue is, UFT is recording or recognising the toolbar buttons. Could you please help me in resolving this issue.
Thanks,
Hello Ramrati,
Thank you for reporting this to us. At this time may I ask if you can provide some additional information about your current testing environment and your AUT. Keep in mind that to use TestAdvantage, you are required to install patch (UFT_00001) aka UFT 11.51, .NET Add-in
1. What version of Infragistics is your AUT used with? 2. Which version of TestAdvantage are you currently using with your AUT?
To obtain the full version of NetAdvantage used in the AUT (application under test) you can look at the version of the NetAdvantage assemblies provided with the AUT or you can ask your developers. To obtain the version from an assembly, right click the assembly in Windows Explorer and select Properties. On the Properties dialog, from the Version tab, look for the Assembly Version.
The full version of TestAdvantage being used can also be obtained from the assemblies. By default the TestAdvantage assemblies are located in the "C:\Program Files\Infragistics\TestAdvantage [version]\Bin" folder.
Have the samples that ship with TestAdvantage work as intended? (record/playback)? They can be found in their default directory C:\All Users\Public Documents
Let me know if you have any questions regarding this matter.
Hello Michael,
I am also facing the similar issue, Where My script was function in QTP 11. Now I am trying to run the same in UFT12.53.
I have installed the Infragestics version 12.1 and the application is also build using 12.1 version only.
Below is the Script developed in QTP 11:
SwfWindow("Zorba-WorkStation").SwfToolbar("MainMenu").Object.ToolbarsManager.Tools tbmgrToolbar, tbmgrClick, "AppToolbar", "Save"
Now the Object is detecting as below:
SwfWindow("Global Property Workstation").SwfObject("_MDIMainForm_Toolbars_Dock_Are")
Please advise.
Thanks
Ram
Hello Mike,
With the QTP version, when we initially developed, it was identified as below.
SwfWindow("Zorba-WorkStation").SwfToolbar("MainMenu")
But with the UFT 12.53 it is detecting as below.
When I try highlight the SwfWindow("Zorba-WorkStation").SwfToolbar("MainMenu") , I am able to highlight the same. But I could not be able to run the script and getting the issue.
SwfWindow("Zorba-WorkStation").SwfToolbar("MainMenu").PerformToolAction tbmgrToolbar, tbmgrClick, "AppToolbar", "Save"
This is the code that I developed earlier.
But now I am getting issue that PerformToolAction method is not supported for the object.
Hi Ram,
The line you said worked in QTP 11, I could not have ever worked as you have it typed for a number of reasons.
For starters, the ".Object.ToolbarsManager.Tools" is telling QTP to get the underlying control Object, and get the ToolbarsManager property, and it's child property Tools. Which our DockArea's do have those properties. Butit would return the .NET ToolsCollection object. Which you could not interact with directly via QTP. You then followed it with tbmgrToolbar, tbmgrClick, "AppToolbar", "Save" which is the foot print for our QTP\UFT specific method PerformToolAction method, that is intended to run on the root QTP\UFT contexted object such as SwfWindow("Global Property Workstation").SwfObject("_MDIMainForm_Toolbars_Dock_Are"). So I can imagine a valid recording interacting with the same Toolbar might be:
SwfWindow("Global Property Workstation").SwfObject("_MDIMainForm_Toolbars_Dock_Are").PerformToolAction tbmgrToolbar, tbmgrClick, "AppToolbar", "Save"
That being said, the SwfWindow identifier also changed, which gives me the impression that this script is either not for the same form, or the underlying form was renamed. So the original script would no longer work on this form either. Even something as simple as :SwfWindow("Zorba-WorkStation").Resize 200,200Because it wouldn't be able to identify the Window correctly.