TestComplete supports testing of various Flash controls. The sections below describe how you can test these controls in detail.
TestComplete can obtain information about controls and objects of Flash 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 Flash applications under the Runtime Loader helper utility.
Include the FlexClient library into the tested Flash application.
Depending on which of the above-mentioned approaches you are using to test your application, different sets of objects, controls and exposed object members are available to TestComplete:
If you are using the debug version of Flash Player, Runtime Loader or the FlexClient library to test a Flash application, it becomes Open, and TestComplete can recognize any visual objects of the application. Besides that, TestComplete adds a special
FlexObject property to each object of the application. This property provides access to the underlying Flash object and its public methods and properties.
If you are using the MSAA engine to test Flash applications, 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.
So, TestComplete can recognize any visual object of the tested Flash application. To test your application, you can perform different actions over controls by using methods and properties provided by TestComplete to any on-screen test object. Besides that, there is a number of Flash controls for which TestComplete provides extended support (see below). For such controls, TestComplete creates special test objects with a number of control-specific methods and properties that make testing of these controls easier. Also, you can test Flash objects by using their native public methods and properties that become accessible if you run the application by using the debug version of Flash Player or the Runtime Loader utility or compile the application with the FlexClient library.
For more information, see What Flash and Flex Methods and Properties are Available for Testing.
A license for the TestComplete Web module.
The Web Testing and Flash Support plugins. 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 plugin is active. If the plugin is not available, run the TestComplete installation in the Repair mode.
TestComplete supports testing of Flash applications that are displayed in the following browsers:
Microsoft Internet Explorer ver. 11.
Mozilla Firefox ver. 68 ESR, 78 ESR, 75 - 80.
If you use a later version of Firefox, check whether a patch is available for it.
Google Chrome ver. 85.
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 85, you will have to upgrade your TestComplete to some later version. We recommend using version 14.61.
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 84.0.4147 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, 6.1, 7.0.0, 7.1, 8.0 - 8.1, 9.2.0, 10.1.0.
To display Flash applications, the Flash Player plugin must be installed in the browser. Testing Flash applications requires Adobe Flash Player version 10.1.102.64 or later. You can download the latest version of Flash Player from Adobe’s web site:
Below is the full list of the Flash controls for which TestComplete provides extended support.
Note that TestComplete provides support for the listed controls as well as for their descendants. However, to make this possible, you need to specify the class name of your inherited control in the corresponding group of the project’s Object Mapping options. For more information, see Object Mapping.
|Button||Adobe Flash CS4 and CS5||fl.controls::Button|
|CheckBox||Adobe Flash CS4 and CS5||fl.controls::CheckBox|
|ComboBox||Adobe Flash CS4 and CS5||fl.controls::ComboBox|
|List||Adobe Flash CS4 and CS5||fl.controls::List|
|RadioButton||Adobe Flash CS4 and CS5||fl.controls::RadioButton|
|TileList||Adobe Flash CS4 and CS5||fl.controls::TileList|