Flex Automation Manager

At the beginning of the year I was investigating the new automation functionality Flex 2.0.1 brought to the table. So I looked into what it would take to implement a tool like QuickTest Pro and made some initial progress, but then got called back to reality and other projects. I mentioned this and several readers of this blog contacted me and asked If they could get the source code or if I could open source it. Well, the code is not in any stage where I could open source it or even show it. It doesn’t work under Flex 3 anymore. But as you asked for it, feel free to have a look at this “experiment”. This code is not an example on how to structure you code or the right way of doing things…it’s rather some dark side coding during a late night session. Be warned only check this out if you are really curious or asked for it :-) Use at your own risk, and don’t ask too many questions: view source here. They are many parts I haven’t even looked into it such as drag&drop, mouse movement emulation, text selection… so Good luck! Also note that Adobe removed from the source code the mx.automation.delegates folder in the Moxie release…These classes are required to make automation work, and I assumed they where part of the SDK and are an important part to understand how the automation is working. So I am not sure what the status on using these classes is.

Posted by Daniel Wanja Mon, 23 Jul 2007 23:19:25 GMT

Read full article 6 comments


Comments

  1. Simeon about 15 hours later:

    I read somewhere the other day that the automation packages are part of the LCDS now. So you are supposed to have a license for that in order to use them. So expect that is why they have been removed from the moxie sdk code.

  2. Daniel Wanja about 15 hours later:

    Hi Simeon,

    There are some .swc file that you can not use unless you use a licensed version of LCDS. Even to use QuickTest Pro I believe you need LCDS. Now each Flex component as an AutomationImplementation that seemd part of the SDK and not part of the Data Services. You don’t need the additional .swc files to run them. I even saw a comment from some of the Adobe guys mentionning I would in order to use them. But again, everyone wanting to proceed in that direction should really clear this out. In fact Adobe should be more clear on what can be done and not with the Implementation classes. If they are an you have a link describing the license for these classes, please provide here as comment. For instance is the TileListItemRendererAutomationImpl class release under the same license than the rest of the components?

  3. Smithfield 1 day later:

    Thanks for source link!

  4. Matt (Adobe) 16 days later:

    Hi, we’ll be sharing more information about our automation plans and why you can’t see the delegate source code in Moxie in the next few months. I think folks will be OK with what we’re doing.

  5. Daniel Wanja 16 days later:

    Hi Matt,

    Now you said too much or not enough :-). That’s good news and I can’t wait to have Flex Automation backed in. That will be such a huge add-on for every developer that takes regression testing seriously.

  6. Tigran Najaryan 5 months later:

    If you are interested in Flex Automation and particularly GUI testing have a look at the upcoming RIATest testing tool at http://riatest.com

    Disclosure: I am a RIATest developer. :-)