Comments on: Flex 2 and Functional Testing – mx.automation classes

By: Renaun Erickson

Renaun Erickson — Tue, 08 Jul 2008 20:16:59 +0000

I haven’t confirmed this actually working myself but the idea is that AccessibilityProperties are what TestComplete will see. So something like this should work for you:

var accessProps:AccessibilityProperties = new AccessibilityProperties();
accessProps.name = “myTestCompleteName”;
myUIComponent.accessibilityProperties = accessProps;

Now in TestComplete when you click on the component it should say something like “myTestCompleteName” for the target name and you can use that in your scripts.

By: Abhe

Abhe — Tue, 08 Jul 2008 18:57:58 +0000

@Renaun
I am evaluating testcomplete for a flex application. Could you post some examples of how to modify flex code to implement the IAccessible interface so as to expose the objects to testcomplete.
thanks

By: Renaun Erickson

Renaun Erickson — Fri, 07 Mar 2008 03:45:13 +0000

@Suni I just recently came across TestComplete. I think since TestComplete relies on IAccessible that its somewhat limited compared to QTP. But it might be enough for your needs, but you have to implement your components or Flex’s components with the IAccessible interface. Which I don’t think all the components in the Flex Framework implement.

By: James Ward - RIA Cowboy » Blog Archive » Matt Raible: Comparing JVM Web Frameworks

Thu, 15 Nov 2007 11:04:24 +0000

[...] “Flash is difficult to integration test” – Not really. Check out: http://flex.org/ACDS/AutomatedTestingInFlex.pdf http://weblogs.macromedia.com/amcleod/archives/2007/01/flex_automation.cfm http://renaun.com/blog/2006/11/27/161/ [...]

By: Sunil

Sunil — Wed, 17 Oct 2007 07:20:53 +0000

Is TestComplete a good substitute for QTP?? It can test Flash also.
Please suggest..

Thanks
Sunil