Hi, At the moment the only way to officially leverage those classes is by using the automation agent API which is sold with an FDS license. FDS is not technically required, it's a licensing thing only. We are looking at changes to that structure for a future release, but there's no change at this time. We have had discussions with other vendors from Mercury, if you have a vendor that you'd like to support Flex you should by all means contact them. I know there are some projects starting up from other people who are examining implementing the system without the FDS requirement, but as you can imagine that's not something that I can support right now :-) Matt
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of jimwash Sent: Sunday, April 15, 2007 10:02 AM To: [email protected] Subject: [flexcoders] flex mx.automation classes It looks like the classes in the mx.automation directory can be used to write software that will allow me to record events for a flex application. But I've not been able to find any documentation telling me how. At least none that doesn't require I buy both the adobe FDS and QTP from Mercury? Is it true you need the flex data service for test automation? If not why do you need an FDS license to use the trial version of QTP. Ideally I don't even have to use QTP, I'm familiar with other test software and would rather not have to move to QTP. Is there any documentation (website, book, example) that explains how to use the mx.automaton classes for my own test adapter. Has anyone had any success using mx.automation code
