Hello,
I am currently using Test Advantage 2011 V2 along with HP UFT 14 (latest version). I observe that the scripts recorded earlier which worked fine are no longer working now. The Swf objects are not getting recognized during playback and when trying to record, the steps involving the Swf objects are not getting recorded. Please help.
Below is the error message I get when I try to play back the scripts I recorded earlier, which were working absolutely fine till this morning:
Could not load file or assembly 'Infragistics2.Win.v11.2, Version=11.2.20112.9000, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb' or one of its dependencies. The system cannot find the file specified.
Function file: C:\Users\pvemuri\Documents\Unified Functional Testing\OLF_QTP_Trade.qflLine (3): "SwfWindow("TradeExplorer").SwfWindow("Olf.Desktop.Controls.DesktopPl").SwfObject("explorerBar").SelectItem "Trading","New Instrument"".
Thanks.
Hi David,
As stated in the blog that I linked to earlier in the thread, "Object doesn't support this action exception" that is typically because your swfconfig.xml file is empty, malformed or pointing to a wrong location for the proxy dlls. Normally just running our version utility and selecting the correct version would correct the issue. If the XML is malformed, our version utility may have issues with reading and writing back to it. When in doubt, wipe out the swfconfig.xml to just:<Controls></Controls>
Then re-run the version utility.
I am actually leaning towards malformed or pointing to the wrong dll location, because ActivateCell exists on the UFT's base implementation, meaning that to say Object doesn't support this action exception, means it read enough to tell UFT don't use there base implementation, but couldn't find it defined in ours. Which that action has been implemented and with little change since the inception of IG TestAutomation.
It the above doesn't work, can you send us your swfconfig.xml file, along with the output of a Process Explorer report of your application's loaded dll's at the time of the exception occurring. It is a small freeware application supplied by Microsoft, you can get it from the link below.https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspxYou can use this to verify what assemblies are loaded in your application under test. Start your application, get it to the point where the controls in question are visible. Run Process Explorer, and find your application in the process list. Highlight it, and press Ctrl+D for the lower pane view showing the loaded dll's. You can then click on Name column header to sort by the DLL names. Right Click on one of the column headers to Select Columns, and make sure on the DLL tab you have Version and path selected. You can then find and identify exactly which version of the assemblies are loaded.
Let me know if that helps,