What is the available support for Adobe Flex applications?
Supports will depend on the version of Adobe Flex versions used to develop an application:
Note(*): Submitted Enhancement Request: QCCR1J30872 - Add Support for Flex SDK 3.x
Note(**): Submitted Enhancement Request: QCCR1J30872 - Add Support for Flex SDK 4.11
For more details and information about Adobe QuickTest Professional (QTP) Flex Add-in, please refer to the document below:
How to Prepare Flex Applications Under Test for Testing with UFT Flex add-in?
Depending on the scenario, end-users can test a Flex application using one of the following methods:
- UFT Flex pre-compiled agent. Compile the application with the relevant Adobe or Apache Flex automation libraries and UFT Flex pre-compiled agent. This agent enables UFT to communicate with the application.
For more information, please refer to the document How to compile Flex application with to work with HP Flex add-in agent?
- UFT Flex Runtime Loader. Open Flex application via the UFT Flex Runtime Loader. For more information, please refer to the document How to test Flex applications using HP Flex Add-in Runtime Loader?
- Adobe Flash Player Debugger. Run Flex applications on UFT client machine where Adobe Flash Player Debugger is installed. For more information, please refer to the document How to setup the Adobe Flash Player Debugger to enable GUI Testing?
Below is a table for some scenarios (not all) and the available methods according to such:
- Backward compatibility with the Adobe Flex Add-in for QTP
UFT Flex Add-in does not provide backward compatibility with the Adobe Flex Add-in for QTP. For more information, please refer to the document https://softwaresupport.hp.com/group/softwaresupport/search-result/-/facetsearch/document/KM00514140
- Cross-domain or cross-host Flex applications
Flex Add-in does not support cross-domain or cross-host Flex applications.
- Object Identification
UFT cannot recognize Flex test objects in windowless Flex applications. A windowless Flex application an wmode parameter defined as opaque or transparent, in the object element of a Flash Player object.
Workaround: Use the window value for the wmode parameter value, or remove the wmode parameter altogether. This workaround requires that users can modify the Web page that contains the Flex application object.
When identifying objects in a Flex application opened in a Web browser, the FlexWindow top-level test object is contained in a Page object.
UFT is not able to recognize a Flex application that is opened by specifying the URL of the SWF file in an Internet Explorer address bar.
Workaround: Create a simple HTML wrapper file to test the SWF file, using the following synatx:
Note: In this example HTML file, the SWF file being tested is named Main.swf.
<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="757" height="518" id="Main">
<param name="movie" value="Main.swf" />
<param name="quality" value="high" />
<param name="bgcolor" value="#ffffff" />
<param name="allowScriptAccess" value="sameDomain" />
<param name="allowFullScreen" value="true" />
For other limitations, please refer to the document https://softwaresupport.hp.com/group/softwaresupport/search-result/-/facetsearch/document/KM00682014