|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.|
|Information in this topic applies only to web tests that implement the classic approach. In cross-platform web tests, TestComplete recognizes third-party controls as standard web controls.|
TestComplete can recognize Spark Spinner controls in Flex applications. It provides special properties and methods that let you retrieve the controls data and simulate user actions on the controls (see below).
Supported component version: Adobe Flex ver. 4.6; Apache Flex ver. 4.9 - 4.14.
In order for TestComplete to be able to work with Spark Spinner controls, the following requirements must be met:
You must have an active license for the TestComplete Web module.
The control’s class name must be specified in the Flex Controls | Spinner group of your project’s Object Mapping options. By default, this group contains the following item:
You can also command the test engine to recognize custom controls as Spark Spinner controls. See below for information about this.
If you experience issues when working with the controls, select File > Install Extensions from the TestComplete main menu and check whether the plugin is active. (You can find the plugin in the Web group.) If the plugin is not available, run the TestComplete installation in the Repair mode.
Recognizing Custom Controls
To command TestComplete to recognize your custom controls as Spark Spinner controls:
Open your project’s Object Mapping options.
Add the control’s class name to the Flex Controls | Spinner group.
If you do not know the control’s name, you can ask the control’s developers, or you can view the control’s property in the Object Browser panel. As an alternative, you can click Add From Screen and select your custom control on screen. TestComplete will retrieve the control’s class name and add it to the selected mapping group automatically. For detailed information, see Object Mapping.
Once the control is mapped, it gets all the properties, methods and actions specific to the Spark Spinner control.
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.
When testing Spark Spinner controls, you can use properties and methods specific to these controls, as well as properties and methods that TestComplete applies to onscreen objects. For the full list of available properties and methods, see the following topics: