Supported Flex Controls

About Supported Flex Controls

Requirements

Supported Browser Versions

Supported Controls

Recognizing Custom Controls

TestComplete can obtain information about controls and objects of Flex applications if you use one of the following approaches for testing:

• Use the debug version of Adobe Flash Player with the FlashInjector.swf helper Flash movie.

• Run Flex applications under the Runtime Loader helper utility.

• Include the FlexClient library into the tested Flex application.

• Use the Microsoft Active Accessibility (MSAA).

Depending on which of the above-mentioned approaches you are using to test your application, different sets of windows, objects, controls and exposed object members become available to TestComplete:

• If your Flex application was compiled with the MSAA engine enabled, TestComplete exposes the on-screen objects for which the accessibility information was provided. These objects contain properties, methods and actions common for on-screen objects as well as a number of extended members added by the MSAA engine.

• If you are using the debug version of Flash Player, Runtime Loader or the FlexClient library to test a Flex application, the application becomes Open, and TestComplete can recognize the application’s visual objects. Besides that, TestComplete adds a special FlexObject property to each object of the application. This property provides access to the underlying Flex object and its public native methods and properties.

For more information, see Testing Flash and Flex Applications - Overview.

• A license for the TestComplete Web module.

• The Adobe Flex Control Support plugin. The plugin provides access to controls via special program objects. It also enables creating table checkpoints for controls that display data in the tabular form. For the full list of these controls, see About Tables Collection.

• The following plugins:

  • Web Testing - Implements web testing, enables testing of web applications running in Internet Explorer, Edge or WebBrowser controls.

  • Firefox Support - Enables testing of web applications running in Mozilla Firefox.

  • Chrome Support - Enables testing of web applications running in Google Chrome.

  • Chromium Embedded Framework Support - Enables web testing in applications created with Chromium Embedded Framework (CEF) or with Electron.

All these plugins are installed and enabled automatically.

If you experience issues when working with the controls, select File | Install Extensions from the TestComplete main menu to check whether the plugins are active. If a plugin is not available, run the TestComplete installation in the Repair mode.

TestComplete supports testing of Flex applications that are displayed in the following browsers:

• Microsoft Internet Explorer ver. 10 - 11.

• Microsoft Edge.

• Mozilla Firefox ver. 60 ESR, 67 - 70.

  If you use a later version of Firefox, check whether a patch is available for it.

• Google Chrome ver. 78.

  If you have a TestComplete version earlier than 12.42, your version of the SmartBear Test Extension will be incompatible with newer versions of the Chrome web browser. To test web applications in Chrome 78, you will have to upgrade your TestComplete to some later version. We recommend using version 14.30.

  If you use a later version of Google Chrome, check whether a patch is available for it.

• Any web browser based on the Microsoft WebBrowser control.

• Embedded Chromium web browser:

  • In applications built with Chromium Embedded Framework (CEF) version 75.0.3773 and earlier.

  • In applications built with Electron version 1.8.2, 2.0.2, 3.0.2, 4.0.2, 5.0.0, 6.0.0, 7.0.0.

To display Flex applications, the Flash Player plugin must be installed in the browser. The required Flash Player version is 10.1.102.64 and later. You can download the latest version of Flash Player from Adobe’s web site:

http://www.adobe.com/go/getflashplayer/

To command TestComplete to recognize your custom Flex controls, open your project’s Object Mapping options and add the control’s class name to the corresponding subgroup of the Flex Controls group. The subgroup name corresponds to your custom control’s type. Once the control is mapped, it gets all the properties, methods and actions specific to the Flex control of the corresponding type.

If the specified custom control does not fit the control’s type, then it may not properly respond to commands that TestComplete sends, so recording or playing back user actions over the tested control will cause errors.