Flex applications show up as Macromedia Flash objects on QTP Object Spy

Issue :

Flex applications show up as Macromedia Flash objects on QTP Object Spy

Potential Causes :

Ensure the your environment works on Automation enabled build from Adobe, Please refer : http://www.adobe.com/devnet/flex/samples/flex_store_v2.html

• If the app does not work,the possible causes are

-Issues with compatibility of QTP-Browser-Flex Plugin/Addin
-The Communication between ActiveX Plugin in the browser for Flex-QTP Automaiton Plugin and QTP is interrupted due to Browser Security settings.

• If the app works then the issue in your environment but your application, the possible causes are

-Application is not compiled with automation swc files i.e. Flex Automation libraries.

Solution :

Issues with compatibility of QTP-Browser-Flex Plugin/Addin

Please refer : http://blogs.adobe.com/vikaschandran/2010/07/10/compatibility-matrix-for-flex-qtp-plugin-3-0-0-and-4-0-0-for-qtp-and-ie-combinations/

Application is compiled with automation swc files i.e. Flex Automation libraries.

Please refer :

Compiling Flex 3 Applications to enable automation

http://blogs.adobe.com/vikaschandran/2010/07/11/compiling-flex-3-applications-to-enable-automaiton/

Compiling Flex 4 Applications to enable automation

http://blogs.adobe.com/vikaschandran/2010/07/15/compiling-flex-4-applications-to-enable-automaiton/

The Communication between ActiveX Plugin in the browser for Flex-QTP Automation Plugin and QTP is interrupted due to Browser Security settings

This can be avoided by ensuring the following

-the TEAPluginIE.dll which is used by IE ActiveX for the Flex-QTP plug-in loads in Internet explorer when QTP is recording

Because if it’s not loaded in IE nothing would work, Process Explorer should help you check the same.

-the behavior of the Object Spy changes [win objects start showing up] if you change i.e. increase the security properties on the browser for internet and intranet

-if you keep both internet and intranet security to medium or low

i.e. basically allowing the Flex-QTP ActiveX component to do its job without hindrance. Everything would work fine.