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
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 firstname.lastname@example.org (I will try to address this more in further posts as time permits 🙂 )