Flash Player has reached end of life on December 31, 2020. Support for Flash and Flex applications is now deprecated in TestComplete and will be removed in a future release. |
TestLeft can simulate user actions and access internal properties and methods of various Flex controls. You can also command your tests to recognize your custom controls as Flex controls to simulate user actions against them.
About Supported Flex Controls
TestLeft 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 TestLeft
-
If your Flex application was compiled with the MSAA engine enabled, TestLeft 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 TestLeft can recognize the application’s visual objects. In addition, TestLeft provides access to the underlying Flex object and its public native methods and properties.
Supported Browser Versions
TestLeft supports testing of Flex controls in web applications displayed in the following browsers:
-
Microsoft Internet Explorer ver. 11.
-
Microsoft Edge ver. 83 - 99 (Chromium-based).
Note: The non-Chromium version of Edge is not supported.
-
Mozilla Firefox ver. 91 ESR, 94 - 98.
-
Google Chrome ver. 99.
Note: If you have a TestLeft version earlier than 2.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 99, you will have to upgrade your TestLeft version to 2.60 or later. -
Any web browser based on the Microsoft WebBrowser control.
Note: The Edge-based WebBrowser control is not supported.
-
Applications with Chromium Embedded Framework control.
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.
Supported Controls
TestLeft recognizes controls by their class name. Below is a full list of the Flex controls that TestLeft supports.
Controls | Library | Classes |
---|---|---|
Button |
Adobe Flex ver. 3.3, 3.4, 3.5, 3.6, 4.0, 4.1, 4.5, 4.6; Apache Flex ver. 4.9 - 4.14 |
mx.controls::Button spark.components::Button |
CheckBox |
Adobe Flex ver. 3.3, 3.4, 3.5, 3.6, 4.0, 4.1, 4.5, 4.6; Apache Flex ver. 4.9 - 4.14 |
mx.controls::CheckBox spark.components::CheckBox |
ComboBox |
Adobe Flex ver. 3.3, 3.4, 3.5, 3.6, 4.0, 4.1, 4.5, 4.6; Apache Flex ver. 4.9 - 4.14 |
mx.controls::ComboBox spark.components::ComboBox |
DataGrid |
Adobe Flex ver. 3.3, 3.4, 3.5, 3.6, 4.0, 4.1, 4.5, 4.6; Apache Flex ver. 4.9 - 4.14 |
mx.controls::DataGrid |
DateChooser |
Adobe Flex ver. 3.3, 3.4, 3.5, 3.6, 4.0, 4.1, 4.5, 4.6; Apache Flex ver. 4.9 - 4.14 |
mx.controls::DateChooser |
DateField |
Adobe Flex ver. 3.3, 3.4, 3.5, 3.6, 4.0, 4.1, 4.5, 4.6; Apache Flex ver. 4.9 - 4.14 |
mx.controls::DateField |
List |
Adobe Flex ver. 3.3, 3.4, 3.5, 3.6, 4.0, 4.1, 4.5, 4.6; Apache Flex ver. 4.9 - 4.14 |
mx.controls::List spark.components::List |
LinkBar |
Adobe Flex ver. 3.3, 3.4, 3.5, 3.6, 4.0, 4.1, 4.5, 4.6; Apache Flex ver. 4.9 - 4.14 |
mx.controls::LinkBar |
NumericStepper |
Adobe Flex ver. 3.3, 3.4, 3.5, 3.6, 4.0, 4.1, 4.5, 4.6; Apache Flex ver. 4.9 - 4.14 |
mx.controls::NumericStepper |
PopUpButton |
Adobe Flex ver. 3.3, 3.4, 3.5, 3.6, 4.0, 4.1, 4.5, 4.6; Apache Flex ver. 4.9 - 4.14 |
mx.controls.PopUpButton |
RadioButton |
Adobe Flex ver. 3.3, 3.4, 3.5, 3.6, 4.0, 4.1, 4.5, 4.6; Apache Flex ver. 4.9 - 4.14 |
mx.controls::RadioButton spark.components::RadioButton |
Spark DataGrid |
Adobe Flex ver. 4.5, 4.6 Apache Flex ver. 4.9 - 4.14 |
spark.components::DataGrid |
Spark DropDownList |
Adobe Flex ver. 3.3, 3.4, 3.5, 3.6, 4.0, 4.1, 4.5, 4.6, 4.6 Apache Flex ver. 4.9 - 4.14 |
spark.components.DropDownList |
Spark Scroller |
Adobe Flex ver. 4.6 Apache Flex ver. 4.9 - 4.14 |
spark.components::Scroller |
Spark Spinner |
Adobe Flex ver. 4.6 Apache Flex ver. 4.9 - 4.14 |
spark.components::Spinner |
ScrollBar |
Adobe Flex ver. 3.3, 3.4, 3.5, 3.6, 4.0, 4.1, 4.5, 4.6; Apache Flex ver. 4.9 - 4.14 |
mx.controls::HScrollBar mx.controls::VScrollBar |
Slider |
Adobe Flex ver. 3.3, 3.4, 3.5, 3.6, 4.0, 4.1, 4.5, 4.6; Apache Flex ver. 4.9 - 4.14 |
mx.controls::HSlider mx.controls::VSlider |
TabBar |
Adobe Flex ver. 3.3, 3.4, 3.5, 3.6, 4.0, 4.1, 4.5, 4.6; Apache Flex ver. 4.9 - 4.14 |
mx.controls::TabBar spark.components::TabBar |
Tree |
Adobe Flex ver. 3.3, 3.4, 3.5, 3.6, 4.0, 4.1, 4.5, 4.6; Apache Flex ver. 4.9 - 4.14 |
mx.controls::Tree |
Recognizing Custom Controls
To command TestLeft to recognize your custom controls as Flex controls, cast your control to the interface of the appropriate type.
If your control does not fit the type of the control, for which the interface provides support, it may improperly respond to commands that TestLeft will send, and simulating user actions against your control may cause errors.