Archive for October, 2009

Flex 3.4 and Flex4 Automation Delegate source code

If you are a Flex Automation test tool user/provider and trying to find how to get the source code of Automation Delegates for Flex SDK 3.4 and 4, get the beta of FlashBuilder downloaded.

FlashBuidler 4 (previously known as FlexBuilder) Beta2 is out and available on Adobe Labs. . 

you can find the source from <installedlocation>/sdks/<sdkversion>/frameworks/projects starting with atuomation.




October 27, 2009 at 10:03 am 13 comments

Flex 4 Automation – New feature list

In Flex4 (the beta available) , automation framework supports the following new features.

  • AIR automation.
  • Marahshalling support for Flex and AIR application. (multi version , different application domain, different security domain etc)
  • Modified custom control handling.
  • Trail for spark automation (only some components are enabled in Beta2)
  • Performance improvement in replaying the script


However the testing tools using the automation framework need to do certain modifications to leverage these new features.


AIR automation of flex controls this includes

  • Windowed application.
  • Multiple window.
  • Drag and drop operations inside AIR applications.

How to get the multiwindow details :
The windows are not children of Application in fact in all-purpose they are independent application instance. Even after closing the main application window the sub application can exists.
Now the automationManager listens to the user interaction on the sub Windows also and will dispatch the record event on these also similar to as it handled on the main window.

The change needed in the tools

You can listen to the  AutomationAirEvent.NEW_AIR_WINDOW from the AutomationManager and get the uniqueId formed for this new window by the automationManager.
You can get the window corresponding to the   id from using getAirWindow  API on the AutomationManager2 passing the window id.  You have to ensure the object received is valid.  (e.g.  getting the window object after the window is closed).

If your tool needs to get the hwnd of the new window,  there is no direct way. However this can be logically handled.  If you would like to know more about this,  or about any of the new features, you can contact me at  (I will try to address this more in further posts as time permits 🙂  )

October 9, 2009 at 6:18 am 9 comments

IE7 and FlexBuilder3 plugin not working for automation using QTP ?

 Are you using FlexBuilder3 plugin and IE7?  Tere was a issue with the Flex Builder 3 Plugin when used with IE7 ( ).

This issue was resolved from Flex Builder 3.2 onwards.   Please follow the steps below to get the latest plugin.

  1. Uninstall the existing flex plugin
  2. Download the last Flex Builder 4 QTP plugin zip file
  3. Unzip it in a permanent location and then click on the Install_QTP_Plugin.bat and then restart your machine.
  4. Now try recording the automatable flexstore application

October 7, 2009 at 6:42 am 6 comments

Using Ant sccript to compile the flex application and enable automation.

If you are using ant script to compile your application and if you would like to link in the automation libraries , you need to use the appropriate compiler arguments. Please  note that placing the automation libraries in the library path and providing the library path using the compiler.library-path wont enable  the applications for automation.

Automation classes wont be added to the application by the compiler just by placing the libraries as the application code does not refer to the automation classes. So the classes needs to be linked in to the application forcefully using the -include-libraries option.

In the ant script this can be used as follows.

This needs to be used in the mxmlc task.

<mxmlc file=”${APP_ROOT}/Main.mxml” keep-generated-actionscript=”true”>

          <compiler.include-libraries dir=”${swf.output}” append=”true”>
                       <include name=”MyComponents.swc” />
                      <include name=”AcmeComponents.swc” />
                    <include name=”DharmaComponents.swc” />


For more details refer

October 7, 2009 at 6:03 am 2 comments

FlashBuilder 4 – Beta2 is out. Spark components automation for trial

FlashBuidler 4 (previously known as FlexBuilder) Beta2 is out and available on Adobe Labs.  check out the new features.

In beta2, Spark components  automation is available for trial. 

Spark Components made automation ready for Beta 2

  • Application
  • Button
  • CheckBox
  • Panel
  • RadioButton
  • ScrollBar
  • TextArea
  • TextInput
  • VGroup
  • HGroup
  • RichEditableText
  • Slider
  • NumericStepper

Automation of these Spark Components is currently supported only for Flex Applications.

Read more about it from the release notes 

Try out this and let us know your feedback.  Refer – automation for the known issues.

October 6, 2009 at 12:13 pm 4 comments

Using FileReference.browse or ?

In the work flow, if you were using FileReference.browse or, the script replay can fail if you are using the Flash player 10.

Flash player 10 security features does not allow action script level programatic reply of events which triggers  the above operations. i.e These operations work only if it was triggered by the user interaction such as actual mouse click or keyboard click.

Since the automation framework replay happens at the action script level (using the low level events being dispatched on the targets), this will be blocked by the security restriction.

The flash player 10 security enhancement documentation states “In Flash Player 9, ActionScript could perform uploads and downloads at any time. With Flash Player 10, the FileReference.browse and operations may be initiated only through ActionScript that originates from user interaction. This includes actions such as clicking the mouse or pressing the keyboard. “

More about it at

October 6, 2009 at 12:02 pm 3 comments


October 2009
« Sep   Dec »

Posts by Month

Posts by Category